What is SOC 2, and what can be quoted for free? Why this site holds none of its text
This page does not quote SOC 2, and it will not. The organisations that write SOC 2, ISO/IEC 27001 and PCI DSS sell the text, and our position — written down in our constitution before any of these pages existed — is that facts plus a short attributed quote with a link are fine, and republishing licensed text is not. So instead of a summary of criteria we are not allowed to print, here is what we can say with a citation behind it: the provisions published freely by public bodies that cover the same ground an auditor will ask you about.
The answer, in the publisher's own words
Access to accounts, which is where most of an audit starts.
IA-2(1) — NIST SP 800-53 Rev 5.2.0 — Multi-factor Authentication to Privileged Accounts.
Implement multi-factor authentication for access to privileged accounts.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "ia-2.1", "class": "SP800-53-enhancement", "title": "Multi-factor Authentication to Privileged Accounts",
"id": "ia", "class": "family", "title": "Identification and Authentication",
Our record: /security-compliance-controls/ia-2-1/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.308(a)(4)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Administrative safeguards.
(4)(i) Standard: Information access management. Implement policies and procedures for authorizing access to electronic protected health information that are consistent with the applicable requirements of subpart E of this part.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.308 Administrative safeguards.
Our record: /security-compliance-controls/164-308-a-4-i/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.308>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
Logging and review.
AU-2a — NIST SP 800-53 Rev 5.2.0 — Event Logging.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Identify the types of events that the system is capable of logging in support of the audit function: [Assignment: organization-defined event types];
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Identify the types of events that the system is capable of logging in support of the audit function: {{ insert: param, au-02_odp.01 }};
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "au-2", "class": "SP800-53", "title": "Event Logging",
"id": "au", "class": "family", "title": "Audit and Accountability",
Our record: /security-compliance-controls/au-2a/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.308(a)(1)(ii)(D) — HIPAA Security Rule (45 CFR part 164, subpart C) — Administrative safeguards.
(D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.
Our record: /security-compliance-controls/164-308-a-1-ii-d/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.308>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
Encryption of stored data.
SC-28 — NIST SP 800-53 Rev 5.2.0 — Protection of Information at Rest.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Protect the [Selection (one or more): confidentiality; integrity] of the following information at rest: [Assignment: organization-defined information at rest].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Protect the {{ insert: param, sc-28_odp.01 }} of the following information at rest: {{ insert: param, sc-28_odp.02 }}.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "sc-28", "class": "SP800-53", "title": "Protection of Information at Rest",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.312(a)(2)(iv) — HIPAA Security Rule (45 CFR part 164, subpart C) — Technical safeguards.
(iv) Encryption and decryption (Addressable). Implement a mechanism to encrypt and decrypt electronic protected health information.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.312 Technical safeguards.
Our record: /security-compliance-controls/164-312-a-2-iv/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
Backup and recovery.
CP-9a — NIST SP 800-53 Rev 5.2.0 — System Backup.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Conduct backups of user-level information contained in [Assignment: organization-defined system components] [Assignment: organization-defined frequency];
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Conduct backups of user-level information contained in {{ insert: param, cp-09_odp.01 }} {{ insert: param, cp-09_odp.02 }};
The same source names the document and the control this provision sits in, which is how the citation above is put together:
"title": "Electronic (OSCAL) Version of NIST SP 800-53 Rev 5.2.0 Controls and SP 800-53A Rev 5.2.0 Assessment Procedures",
"id": "cp-9", "class": "SP800-53", "title": "System Backup",
"id": "cp", "class": "family", "title": "Contingency Planning",
Our record: /security-compliance-controls/cp-9a/. Quoted from <https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.308(a)(7)(ii)(A) — HIPAA Security Rule (45 CFR part 164, subpart C) — Administrative safeguards.
(A) Data backup plan (Required). Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information.
Our record: /security-compliance-controls/164-308-a-7-ii-a/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.308>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
And the part of an audit that is about paper rather than software: keeping the documentation, and keeping it long enough.
164.316(a) — HIPAA Security Rule (45 CFR part 164, subpart C) — Policies and procedures and documentation requirements.
(a) Standard: Policies and procedures. Implement reasonable and appropriate policies and procedures to comply with the standards, implementation specifications, or other requirements of this subpart, taking into account those factors specified in § 164.306(b)(2)(i), (ii), (iii), and (iv). This standard is not to be construed to permit or excuse an action that violates any other standard, implementation specification, or other requirements of this subpart. A covered entity or business associate may change its policies and procedures at any time, provided that the changes are documented and are implemented in accordance with this subpart.
The same source names the document and the control this provision sits in, which is how the citation above is put together:
§ 164.316 Policies and procedures and documentation requirements.
Our record: /security-compliance-controls/164-316-a/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.316>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
164.316(b)(2)(i) — HIPAA Security Rule (45 CFR part 164, subpart C) — Policies and procedures and documentation requirements.
(i) Time limit (Required). Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.
Our record: /security-compliance-controls/164-316-b-2-i/. Quoted from <https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.316>, last checked 2026-11-15, due to be re-checked by 2026-12-15.
None of that is a map of SOC 2's criteria, and it is not offered as one. It is a list of published obligations that bear on the same subjects, each with the publisher's own sentence, so that an engineer preparing for an audit has something citable to build against while the auditor's own framework stays with the auditor.
What is not in our records, checked
There is no SOC 2, ISO/IEC 27001 or PCI DSS text anywhere in the records this site publishes. That is checked on every build, not promised.
Checked, not asserted: none of trust services criteria, SOC 2, ISO/IEC 27001, ISO 27001, PCI DSS, cardholder data appears anywhere in the 2,022 provisions we hold of NIST SP 800-53 and the HIPAA Security Rule, which is every provision this site publishes. That is a search of the publisher's own words, and it is what the gate on this page tests; if one of those words turned up, this page would stop being built.
The check runs over the provisions this family of pages is built from, every time the pages are rebuilt, and the build fails if one of those phrases turns up. A promise in a footer is worth less than a test that fails.
What we have not read
What we cannot tell you is what SOC 2 requires, because we do not hold the document. Nor can we tell you whether satisfying the provisions above would satisfy an auditor: that depends on scope, on the trust services categories chosen, and on the auditor. The published rules quoted here are a floor somebody can check, not a crosswalk.
The same answer for a machine
- The provisions dataset — what we do hold: NIST SP 800-53 and the HIPAA Security Rule, verbatim, one provision per record.
The other questions answered here
Does HIPAA apply to my app?, What does HIPAA require software to do?, Does HIPAA require encryption at rest, and which algorithm?, What must I log for HIPAA, and how long must records be kept?, What session timeout do HIPAA and NIST require?, What password rules does NIST state?, Do I need multi-factor sign-in, and under which rule?, How fast must I report a breach, by law and by state?, Which state privacy laws apply to my app, by revenue and number of consumers?, Which NIST 800-53 controls bear on a database, on object storage, on logs and on backups?, Which cryptographic algorithms and TLS certificate lifetimes stop being acceptable, and when?.
All of them are listed on the question list.
What this page is
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.
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.
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.