Compliance for developers: the questions, answered in the rules' own words
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
- Does HIPAA apply to my app? — The applicability section, and why the rule cannot tell you whether you are a covered entity.
- What does HIPAA require software to do? — 45 CFR 164.312 in full, each provision quoted, with which are Required and which Addressable.
- Does HIPAA require encryption at rest, and which algorithm? — The encryption provisions verbatim, what Addressable means in the rule's own words, and the algorithm the rule does not name.
- What must I log for HIPAA, and how long must records be kept? — Audit controls, activity review, the six-year documentation clock, and what the rule does not say about log retention.
- What session timeout do HIPAA and NIST require? — Automatic logoff and session termination quoted in full, and the minutes figure that is in neither rule.
- What password rules does NIST state? — IA-5(1) quoted statement by statement, and the expiry rule it does not contain.
- Do I need multi-factor sign-in, and under which rule? — The rule that does require multi-factor, the rule that does not, and which accounts each means.
- How fast must I report a breach, by law and by state? — Each state's notification clock as the statute words it, and why a single number is the wrong shape of answer.
- Which state privacy laws apply to my app, by revenue and number of consumers? — Consumer-count and revenue thresholds per state, with the AND/OR logic that decides applicability.
- Which NIST 800-53 controls bear on a database, on object storage, on logs and on backups? — Controls grouped by the part of the system you are building, with the mapping named as ours rather than NIST's.
- What is SOC 2, and what in it can and cannot be quoted for free? — Our licence position on SOC 2, ISO 27001 and PCI DSS, checked rather than promised, and the free provisions covering the same ground.
- Which cryptographic algorithms and TLS certificate lifetimes stop being acceptable, and when? — The dated TLS step-down from the Baseline Requirements, and each algorithm's current and planned status.
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:
- NIST SP 800-53 and the HIPAA Security Rule, one provision at a time — 2,022 records with a quote and a source. One record is one obligation, keyed the way its publisher cites it, so a lookup by control number is a single hop.
- state data breach notification clocks — 18 records with a quote and a source. How fast each state's statute says the people affected must be told, and what triggers notice to the attorney general.
- state consumer privacy law thresholds — 18 records with a quote and a source. The revenue and consumer-count numbers that decide whether a state's privacy law binds you at all.
- federal record retention periods — 24 records with a quote and a source. How long a federal regulation requires a record to be kept, and what starts the clock.
- NIST cryptographic algorithm status — 21 records with a quote and a source. What is approved, deprecated and disallowed, and the post-quantum standards that replace it.
- dated TLS certificate requirements — 49 records with a quote and a source. The CA/Browser Forum, Chrome and Mozilla deadlines, each with the date it takes effect.
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.