Reference Source

Compliance for developers: the questions, answered in the rules' own words

Published .

A developer asked to make something compliant is handed a word, not a rule: HIPAA, SOC 2, encryption at rest. The published rules do answer most of those questions, in one or two sentences, and the sentences are short. The hard part is that they are published as whole documents, so the answer to "does the rule name an algorithm" takes an afternoon and usually gets answered by somebody selling something instead. Each page here takes one question, answers it out of the publisher's own sentence, links the record and the page that sentence was quoted from, and then says what the rule does NOT say, which is the half that is missing almost everywhere else.

The questions

What these answers are built out of

Every answer on these pages is a sentence out of one of these record sets, printed as the record prints it:

What is not here, and why

SOC 2, ISO/IEC 27001 and PCI DSS are not quoted anywhere on these pages. The bodies that write those documents sell the text, and our position, written down in our constitution, is that facts plus a short attributed quote with a link are fine but republishing licensed text is not. So nothing here quotes a trust services criterion or an ISO clause. What can be quoted is the rules the public bodies publish — the HIPAA Security Rule, NIST SP 800-53, federal retention regulations, state statutes and the CA/Browser Forum's requirements — and that is what every answer here is built out of.

If a question you asked is not here, the records underneath these pages hold a great deal more than the pages print, and all of it is addressable without us: every dataset linked above has a machine-readable twin, there is an address that answers by component at /api/requirements, and there is a server at /mcp for a coding assistant that speaks it.

What these pages are

This page is assembled automatically out of the records named on it. No sentence of a rule on it is ours: every one is quoted from the publisher that wrote it, with a link to the page it was quoted from and the date we last checked that page.

This is not legal advice and it is not a statement that any system complies with anything. A provision quoted here is a sentence from a published document, not a finding about your software. Who decides: your own counsel, your auditor, and the regulator.