800-53 · CP Contingency Planning
CP-10
System Recovery and Reconstitution
frameworkNIST SP 800-53 Rev 5.2
sectionCP Contingency Planning
csf 2.0RC.RP-01 RC.RP-02 RC.RP-05
topicsRecovery Planning, Comms & Restore, Disaster Recovery
frameworks7 4 2
Official textProvide for the recovery and reconstitution of the system to a known state within [Assignment: organization-defined organization-defined time period consistent with recovery time and recovery point objectives] after a disruption, compromise, or failure.NIST SP 800-53 Rev 5.2 control statement (public domain)
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | ID.IM-04PR.IR-03RC.CO-03RC.CO-04RC.RP-01RC.RP-02RC.RP-05 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved; Mechanisms are implemented to achieve resilience requirements in normal and adverse situations… | Crosswalk | Same topic: Recovery Planning, Disaster Recovery, Comms & Restore |
| ISO 27001 | A.5.26A.5.29A.5.30A.8.14Clause 7.4 | Response to information security incidents; Information security during disruption… | Crosswalk | Same topic: Comms & Restore, Recovery Planning, Disaster Recovery |
| CIS v8.1 | CIS 17.6CIS 11.1 | Define Mechanisms for Communicating During Incident Response; Establish and Maintain a Data Recovery Process | Crosswalk | Same topic: Comms & Restore, Recovery Planning, Disaster Recovery |
| SOC 2 | A1.2A1.3CC2.3CC7.5 | Environmental protections, backups and recovery infrastructure; Testing recovery plan procedures… | Editorial | Same topic: Disaster Recovery, Recovery Planning, Comms & Restore (editorial pick) |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Crosswalk | Same topic: Recovery Planning, Disaster Recovery8 loosely related (not mappings)12.10.2 Incident response plan reviewed and tested annually Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping 1.2.4 Accurate account-data flow diagram maintained Only shares CSF RC.RP-02: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF RC.RP-05: related, not a mapping 11.4.4 Penetration test findings corrected and retested Only shares CSF RC.RP-05: related, not a mapping 12.10.3 Incident response staff available around the clock Only shares CSF RC.RP-01: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF RC.RP-02: related, not a mapping |
| CMMC | IR.L2-3.6.2 | Incident Reporting | Crosswalk | Same topic: Comms & Restore1 loosely related (not mappings) |
| HIPAA | §164.308(a)(7)§164.308(a)(7)(ii)(B)§164.308(a)(7)(ii)(D)§164.308(a)(7)(ii)(C) | Contingency Plan; Disaster Recovery Plan… | Crosswalk | Same topic: Recovery Planning, Disaster Recovery NIST HIPAA → SP 800-53 crosswalk 2 loosely related (not mappings)§164.308(a)(6) Security Incident Procedures Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping §164.308(a)(6)(ii) Response and Reporting Only shares CSF RC.RP-01, RC.RP-02: related, not a mapping |
| GDPR | Art.32(1)(c)Art.34(1) | Security of processing; Communication of a personal data breach to the data subject | Editorial | Same topic: Recovery Planning, Disaster Recovery, Comms & Restore (editorial pick) |
| NIS2 | 4.14.24.3 | Business continuity and disaster recovery plan; Backup management… | Crosswalk | Same topic: Recovery Planning, Disaster Recovery, Comms & Restore |
| Essential Eight | ISM-1515 | Restoration of data, applications and settings from backups to a common point in time… | Editorial | Same topic: Disaster Recovery (editorial pick) |
| DORA | Art.11(2)(e)Art.11(3)Art.11(6)Art.11(7)Art.12(4)Art.12(6) | Response and recovery; Response and recovery… | Editorial | Same topic: Comms & Restore, Recovery Planning, Disaster Recovery (editorial pick) |
| CPS 234 | — | No requirement | No mapping in our data | No mapping in our data (CPS 234 is principles-based and its links are editorial). |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.