File size: 4,914 Bytes
91c9193 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 | ---
pretty_name: "Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words"
license: other
license_name: source-terms-cited
license_link: https://referencesource.org/security-compliance-controls/
language:
- en
tags:
- reference-data
- provenance
- referencesource-org
configs:
- config_name: default
data_files:
- split: train
path: data/records.jsonl
---
# Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words
**Canonical, always-current version: https://referencesource.org/security-compliance-controls/**
Machine-readable: https://referencesource.org/security-compliance-controls/data.json — this mirror is a point-in-time copy.
- **Last verified:** 2026-11-15
- **Stale after:** 2026-12-15 (past this date, prefer the canonical copy —
it re-verifies on a cadence this snapshot does not)
- **Records:** 2022
Every control in NIST SP 800-53 Rev 5 and every paragraph of the HIPAA Security Rule, cut one provision at a time, each with the publisher's own words as the record's quote. One record is one obligation: a control with five lettered statements becomes five records, keyed the way the publisher cites them (SC-28, SC-28(1), AC-2a, 164.312(a)(2)(iv)), so a reader or an agent that has been handed a control number gets that control's text and nothing else. Answers 'what does NIST SP 800-53 SC-28 require', 'what does HIPAA 164.312(a)(2)(iv) actually say about encryption', 'which published controls cover audit logging', and 'what is the organization-defined parameter in AC-12'. The hard part is not finding the documents — NIST publishes the catalogue as machine-readable OSCAL and the eCFR publishes the rule as XML — it is that both are published as whole documents, so a coding assistant asked to implement 'SC-28' either reads a 1,200-page catalogue or guesses. This dataset is the retrieval layer: provision in, the publisher's sentence out. It does not say how to implement anything; the control's own text is the whole of what is published here. NIST's machine-readable text leaves a placeholder where a value is the organisation's to decide ('Protect the {{ insert: param, sc-28_odp.01 }} of ...'), so every record that carries one also carries the same sentence with each placeholder resolved from the catalogue's own parameter labels and kept in square brackets — '[Selection (one or more): confidentiality; integrity]' — which is how NIST's own HTML rendering reads, and which is a sentence a person or a coding assistant can actually use. The verbatim text, placeholders and all, stays on the record as the evidence. SOC 2, ISO 27001 and PCI DSS are deliberately absent: that text is copyrighted and may not be republished.
## Provenance — what every record carries
Every record carries `source` (the URL the value was read from) and
`source_quote` (a verbatim quote from that page stating it). A value you
cannot check against its page is indistinguishable from an invented one;
these can all be checked. Each record is also individually addressable on
the canonical site at its `url`.
## Licence position
Both sources are US government works in the public domain: NIST SP 800-53 is published by NIST with its OSCAL rendering in a public GitHub repository, and the Code of Federal Regulations is published by the Office of the Federal Register. Each record links back to the exact API URL it was cut from and names the publisher's own page for the document. No text from SOC 2, ISO/IEC 27001 or PCI DSS appears anywhere in this dataset, because that text is copyrighted.
Facts are not copyrightable; what this dataset takes from each source is a
fact plus a short attributed quote linking back to the page that states it.
## Sources
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.302
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.306
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.308
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.310
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.312
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.314
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.316
- https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164§ion=164.318
- https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json
## Fields
See any record in `data/records.jsonl` — field names are self-describing,
and the canonical page for each record renders them with labels:
https://referencesource.org/security-compliance-controls/
|