# NIST SP 800-53 Rev. 5 CP-10 — System Recovery And Reconstitution - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-10-system-recovery-and-reconstitution - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › CP — Contingency Planning - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `CP-10`·high·Component: **Contingency Planning** ## What this control requires > Implement transaction recovery for transaction-based systems using rollback/journaling to ensure data integrity and recoverability after disruptions. This control supports the Disaster Recovery capability within the Contingency Planning family. > > — NIST SP 800-53 Rev. 5, Control CP-10 ### In plain English Implement transaction recovery for transaction-based systems using rollback/journaling to ensure data integrity and recoverability after disruptions. In practice, this means you can prove you data system-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **Contingency Planning**, the assessor will trace your implementation back to the catalogue reference (Control CP-10) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Data.** Document the trigger, the owner and the cadence. - **Review.** Document the trigger, the owner and the cadence. - **System.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Testing,.** Document the trigger, the owner and the cadence. - **Scope:** system, review, recovery, capability, systems, implement, integrity, code. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: System Recovery And Reconstitution. ## Common pitfalls - CI security checks set to warn-only; the merge button is faster than the security feedback. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**BSI C5:2020 DEV-08** — Version Control](https://support.icompaas.com/compliance/bsi-c5-2020/dev-08-version-control) - [**SOC 2 (2017 TSC) A1.3** — Testing of System Recovery Procedures](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/a1-3-testing-of-system-recovery-procedures) - [**NIST SP 800-171 Rev. 3 3.14.2** — Malicious Code Protection](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-14-2-malicious-code-protection) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-14** — Criticality Analysis](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-14-criticality-analysis) - [**Control SC-40(1)** — Electromagnetic Interference](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-40-1-electromagnetic-interference) - [**Control CP-10(2)** — Transaction Recovery](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-10-2-transaction-recovery) - [**Control SI-8(3)** — Continuous Learning Capability](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-8-3-continuous-learning-capability) - [**Control AU-9(2)** — Store On Separate Physical Systems Or Components](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/au-9-2-store-on-separate-physical-systems-or-components) - [**Control SI-22** — Information Diversity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/si-22-information-diversity) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control CP-10` Topics: governance risksecure developmentcode review testingdevsecopsbackup recovery ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.