Which NIST 800-53 controls bear on a database, object storage, logs, backups, keys and transport?
A developer knows what they are building, not which control number governs it. The catalogue is organised the other way round, which is why this page exists. One thing has to be said plainly first: the grouping below is OURS. No publisher says that somebody building a database should read these particular controls. The control text is NIST's, quoted exactly; the decision about which heading to print it under is a judgement we made, and you can disagree with it by reading the catalogue directly.
The answer, in the publisher's own words
A database, or any store of records at rest.
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.
SC-28(1) — NIST SP 800-53 Rev 5.2.0 — Cryptographic Protection.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [Assignment: organization-defined system components or media]: [Assignment: organization-defined information].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on {{ insert: param, sc-28.01_odp.02 }}: {{ insert: param, sc-28.01_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": "sc-28.1", "class": "SP800-53-enhancement", "title": "Cryptographic Protection",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28-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.
Object storage, buckets and files — the same at-rest controls apply, and these two are the ones that bear on what happens to the media and to data taken out of the live system.
SC-28(2) — NIST SP 800-53 Rev 5.2.0 — Offline Storage.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Remove the following information from online storage and store offline in a secure location: [Assignment: organization-defined information].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Remove the following information from online storage and store offline in a secure location: {{ insert: param, sc-28.02_odp }}.
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.2", "class": "SP800-53-enhancement", "title": "Offline Storage",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28-2/. 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.
MP-6a — NIST SP 800-53 Rev 5.2.0 — Media Sanitization.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Sanitize [Assignment: organization-defined organization-defined system media] prior to disposal, release out of organizational control, or release for reuse using [Assignment: organization-defined organization-defined sanitization techniques and procedures] ; and
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Sanitize {{ insert: param, mp-6_prm_1 }} prior to disposal, release out of organizational control, or release for reuse using {{ insert: param, mp-6_prm_2 }} ; and
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": "mp-6", "class": "SP800-53", "title": "Media Sanitization",
"id": "mp", "class": "family", "title": "Media Protection",
Our record: /security-compliance-controls/mp-6a/. 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.
Logs and the audit trail.
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.
AU-2e — 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:
Review and update the event types selected for logging [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:
Review and update the event types selected for logging {{ insert: param, au-02_odp.04 }}.
Our record: /security-compliance-controls/au-2e/. 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.
AU-6a — NIST SP 800-53 Rev 5.2.0 — Audit Record Review, Analysis, and Reporting.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Review and analyze system audit records [Assignment: organization-defined frequency] for indications of [Assignment: organization-defined inappropriate or unusual activity] and the potential impact of the inappropriate or unusual activity;
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Review and analyze system audit records {{ insert: param, au-06_odp.01 }} for indications of {{ insert: param, au-06_odp.02 }} and the potential impact of the inappropriate or unusual activity;
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-6", "class": "SP800-53", "title": "Audit Record Review, Analysis, and Reporting",
"id": "au", "class": "family", "title": "Audit and Accountability",
Our record: /security-compliance-controls/au-6a/. 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.
AU-11 — NIST SP 800-53 Rev 5.2.0 — Audit Record Retention.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Retain audit records for [Assignment: organization-defined time period] to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Retain audit records for {{ insert: param, au-11_odp }} to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.
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-11", "class": "SP800-53", "title": "Audit Record Retention",
"id": "au", "class": "family", "title": "Audit and Accountability",
Our record: /security-compliance-controls/au-11/. 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.
Backups, and the part everybody skips, which is proving a backup restores.
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.
CP-9(1) — NIST SP 800-53 Rev 5.2.0 — Testing for Reliability and Integrity.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Test backup information [Assignment: organization-defined organization-defined frequency] to verify media reliability and information integrity.
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Test backup information {{ insert: param, cp-9.1_prm_1 }} to verify media reliability and information integrity.
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.1", "class": "SP800-53-enhancement", "title": "Testing for Reliability and Integrity",
"id": "cp", "class": "family", "title": "Contingency Planning",
Our record: /security-compliance-controls/cp-9-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.
CP-9(8) — NIST SP 800-53 Rev 5.2.0 — Cryptographic Protection.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined backup information].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of {{ insert: param, cp-09.08_odp }}.
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.8", "class": "SP800-53-enhancement", "title": "Cryptographic Protection",
"id": "cp", "class": "family", "title": "Contingency Planning",
Our record: /security-compliance-controls/cp-9-8/. 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.
Keys and secrets.
SC-12 — NIST SP 800-53 Rev 5.2.0 — Cryptographic Key Establishment and Management.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignment: organization-defined requirements].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: {{ insert: param, sc-12_odp }}.
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-12", "class": "SP800-53", "title": "Cryptographic Key Establishment and Management",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-12/. 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.
SC-28(3) — NIST SP 800-53 Rev 5.2.0 — Cryptographic Keys.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Provide protected storage for cryptographic keys [Selection: [Assignment: organization-defined safeguards]; hardware-protected key store].
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Provide protected storage for cryptographic keys {{ insert: param, sc-28.03_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": "sc-28.3", "class": "SP800-53-enhancement", "title": "Cryptographic Keys",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-28-3/. 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.
The API and anything in transit.
SC-8 — NIST SP 800-53 Rev 5.2.0 — Transmission Confidentiality and Integrity.
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 transmitted information.
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-08_odp }} of transmitted information.
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-8", "class": "SP800-53", "title": "Transmission Confidentiality and Integrity",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-8/. 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.
SC-8(1) — NIST SP 800-53 Rev 5.2.0 — Cryptographic Protection.
As the catalogue's own rendering reads, with each value the organisation defines in square brackets:
Implement cryptographic mechanisms to [Selection (one or more): prevent unauthorized disclosure of information; detect changes to information] during transmission.
The same provision in the publisher's machine-readable text, which is this record's evidence and prints a placeholder where that value goes:
Implement cryptographic mechanisms to {{ insert: param, sc-08.01_odp }} during transmission.
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-8.1", "class": "SP800-53-enhancement", "title": "Cryptographic Protection",
"id": "sc", "class": "family", "title": "System and Communications Protection",
Our record: /security-compliance-controls/sc-8-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.
Each citation above is in the form the publisher uses, so it can go straight into a code comment or a pull request description and be checked by whoever reads it.
What the catalogue does not say
The catalogue's own text names none of these components. It does not say database, bucket, object storage, container or any product name.
Checked, not asserted: none of database, bucket, object storage, Postgres, MySQL, container, Kubernetes appears anywhere in the fifteen provisions we hold of the provisions printed on this page. 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.
That is the gap this page fills and also its limitation: the words a developer types are not the words the catalogue uses, so somebody has to do the mapping, and the honest thing is to say who. We did. If you want the mapping as a service rather than as a page, the address below takes the component name and returns the provisions, naming the same mapping as ours in every answer.
The same answer for a machine
- Requirements by component, as an address — the same answer as JSON or plain text, no account and no client to install.
- The catalogue as data — every provision as its own record, keyed the way NIST cites it.
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?, What is SOC 2, and what in it can and cannot be quoted for free?, 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.