800-53 · CP Contingency Planning
CP-2
Contingency Plan
frameworkNIST SP 800-53 Rev 5.2
sectionCP Contingency Planning
csf 2.0ID.IM-01 ID.IM-02 ID.IM-03 ID.IM-04 PR.IR-02 RC.CO-04 RC.RP-03
topicsRecovery Planning
frameworks5 4 2
Official texta. Develop a contingency plan for the system that:
1. Identifies essential mission and business functions and associated contingency requirements;
2. Provides recovery objectives, restoration priorities, and metrics;
3. Addresses contingency roles, responsibilities, assigned individuals with contact information;
4. Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
5. Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
6. Addresses the sharing of contingency information; and
7. Is reviewed and approved by [Assignment: organization-defined organization-defined personnel or roles];
b. Distribute copies of the contingency plan to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
c. Coordinate contingency planning activities with incident handling activities;
d. Review the contingency plan for the system [Assignment: organization-defined frequency];
e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;
f. Communicate contingency plan changes to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
h. Protect the contingency plan from unauthorized disclosure and modification.NIST SP 800-53 Rev 5.2 control statement (public domain)
1. Identifies essential mission and business functions and associated contingency requirements;
2. Provides recovery objectives, restoration priorities, and metrics;
3. Addresses contingency roles, responsibilities, assigned individuals with contact information;
4. Addresses maintaining essential mission and business functions despite a system disruption, compromise, or failure;
5. Addresses eventual, full system restoration without deterioration of the controls originally planned and implemented;
6. Addresses the sharing of contingency information; and
7. Is reviewed and approved by [Assignment: organization-defined organization-defined personnel or roles];
b. Distribute copies of the contingency plan to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
c. Coordinate contingency planning activities with incident handling activities;
d. Review the contingency plan for the system [Assignment: organization-defined frequency];
e. Update the contingency plan to address changes to the organization, system, or environment of operation and problems encountered during contingency plan implementation, execution, or testing;
f. Communicate contingency plan changes to [Assignment: organization-defined organization-defined key contingency personnel (identified by name and/or by role) and organizational elements];
g. Incorporate lessons learned from contingency plan testing, training, or actual contingency activities into contingency testing and training; and
h. Protect the contingency plan from unauthorized disclosure and modification.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-04RC.RP-01RC.RP-02 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved; The recovery portion of the incident response plan is executed once initiated from the incident response process… | Crosswalk | Same topic: Recovery Planning3 loosely related (not mappings)PR.IR-02 The organization's technology assets are protected from environmental threats Only shares CSF PR.IR-02: related, not a mapping RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Only shares CSF RC.CO-04: related, not a mapping RC.RP-03 The integrity of backups and other restoration assets is verified before using them for restoration Only shares CSF RC.RP-03: related, not a mapping |
| ISO 27001 | A.5.29A.5.30A.5.2A.8.6A.8.14Clause 7.5.1Clause 7.5.2Clause 7.5.3 | Information security during disruption; ICT readiness for business continuity… | Crosswalk | Same topic: Recovery Planning NIST SP 800-53 → ISO 27001 mapping 10 loosely related (not mappings)A.7.5 Protecting against physical and environmental threats Only shares CSF PR.IR-02: related, not a mapping …and 2 more in the downloads |
| CIS v8.1 | CIS 11.1 | Establish and Maintain a Data Recovery Process | Editorial | Same topic: Recovery Planning (editorial pick)4 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04: related, not a mapping CIS 17.6 Define Mechanisms for Communicating During Incident Response Only shares CSF RC.CO-04: related, not a mapping CIS 11.4 Establish and Maintain an Isolated Instance of Recovery Data Only shares CSF RC.RP-03: related, not a mapping |
| SOC 2 | A1.3CC7.5 | Testing recovery plan procedures; Recovering from identified security incidents | Editorial | Same topic: Recovery Planning (editorial pick)3 loosely related (not mappings)A1.2 Environmental protections, backups and recovery infrastructure Only shares CSF RC.RP-03: related, not a mapping |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Crosswalk | Same topic: Recovery Planning10 loosely related (not mappings)12.10.3 Incident response staff available around the clock Only shares CSF ID.IM-04, RC.CO-04: related, not a mapping 5.3.2 Periodic scans or continuous behavioural analysis Only shares CSF RC.RP-03: related, not a mapping 9.1.1 Physical security policies documented and kept current Only shares CSF PR.IR-02: related, not a mapping 9.4.1.2 Security of offline backup location reviewed annually Only shares CSF RC.RP-03: related, not a mapping 9.2.1.1 Access to sensitive areas monitored by camera or access control Only shares CSF PR.IR-02: related, not a mapping …and 2 more in the downloads |
| CMMC | IR.L2-3.6.1MP.L2-3.8.9PE.L2-3.10.6 | Incident Handling; Protect Backups… | No mapping. Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-04…: related, not a mapping | |
| HIPAA | §164.308(a)(7)§164.308(a)(7)(ii)(B)§164.308(a)(7)(ii)(C)§164.308(a)(7)(ii)(D)§164.308(a)(7)(ii)(E)§164.310(a)(2)(i)§164.312(a)(2)(ii) | Contingency Plan; Disaster Recovery Plan… | Crosswalk | Same topic: Recovery Planning NIST HIPAA → SP 800-53 crosswalk 7 loosely related (not mappings)§164.308(a)(6)(ii) Response and Reporting Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.310(a)(2)(ii) Facility Security Plan Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, ID.IM-04…: related, not a mapping §164.308(a)(6) Security Incident Procedures Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.CO-04: related, not a mapping §164.312(c) Integrity Only shares CSF ID.IM-01, ID.IM-02, ID.IM-03, RC.RP-03: related, not a mapping |
| GDPR | Art.32(1)(c) | Security of processing | Editorial | Same topic: Recovery Planning (editorial pick)1 loosely related (not mappings)Art.34(1) Communication of a personal data breach to the data subject Only shares CSF RC.CO-04: related, not a mapping |
| NIS2 | 4.1 | Business continuity and disaster recovery plan | Crosswalk | Same topic: Recovery Planning |
| Essential Eight | ISM-1511ISM-1515ISM-1705ISM-1706 | Backups of data, applications and settings are performed and retained in accordance…; Restoration of data, applications and settings from backups to a common point in time…… | No mapping. Only shares CSF RC.RP-03: related, not a mapping+7 more loosely related (not mappings)ISM-1707 Privileged user accounts (excluding backup administrator accounts) are prevented from… Only shares CSF RC.RP-03: related, not a mapping ISM-1708 Backup administrator accounts are prevented from modifying and deleting backups during… Only shares CSF RC.RP-03: related, not a mapping ISM-1810 Backups of data, applications and settings are synchronised to enable restoration to a… Only shares CSF RC.RP-03: related, not a mapping ISM-1811 Backups of data, applications and settings are retained in a secure and resilient manner Only shares CSF RC.RP-03: related, not a mapping …and 3 more in the downloads | |
| DORA | Art.11(3)Art.12(6) | Response and recovery; Backup policies and procedures, restoration and recovery procedures and methods | Editorial | Same topic: Recovery Planning (editorial pick)7 loosely related (not mappings)Art.12(1) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF RC.RP-03: related, not a mapping Art.12(2) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF RC.RP-03: related, not a mapping Art.12(3) Backup policies and procedures, restoration and recovery procedures and methods Only shares CSF RC.RP-03: related, not a mapping |
| 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.