800-53 · CP Contingency Planning
CP-2(8)
Identify Critical Assets
frameworkNIST SP 800-53 Rev 5.2
sectionCP Contingency Planning
csf 2.0GV.OC-04
topicsBusiness Continuity
frameworks5 3 5
Official textIdentify critical system assets supporting [Selection: all; essential] mission and business functions.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 | GV.OC-04PR.IR-03RC.RP-04 | Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated; Mechanisms are implemented to achieve resilience requirements in normal and adverse situations… | Crosswalk | Same topic: Business Continuity |
| ISO 27001 | A.5.29A.5.30A.8.14 | Information security during disruption; ICT readiness for business continuity… | Crosswalk | Same topic: Business Continuity3 loosely related (not mappings)A.5.20 Addressing information security within supplier agreements Only shares CSF GV.OC-04: related, not a mapping A.5.31 Legal, statutory, regulatory and contractual requirements Only shares CSF GV.OC-04: related, not a mapping Clause 4.2 Understanding the needs and expectations of interested parties Only shares CSF GV.OC-04: related, not a mapping |
| CIS v8.1 | — | No requirement | No mapping in our data | No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards). |
| SOC 2 | A1.1A1.2CC9.1 | Capacity management to meet availability commitments; Environmental protections, backups and recovery infrastructure… | Editorial | Same topic: Business Continuity (editorial pick)1 loosely related (not mappings)CC3.1 Objectives specified clearly enough to identify risks Only shares CSF GV.OC-04: related, not a mapping |
| PCI DSS | 12.10.1 | Incident response plan ready to activate | Crosswalk | Same topic: Business Continuity |
| CMMC | — | No requirement | No mapping in our data | No mapping in our data. |
| HIPAA | §164.308(a)(7)(ii)(C)§164.308(a)(7)(ii)(E) | Emergency Mode Operation Plan; Applications and Data Criticality Analysis | Crosswalk | Same topic: Business Continuity NIST HIPAA → SP 800-53 crosswalk 5 loosely related (not mappings)§164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF GV.OC-04: related, not a mapping |
| GDPR | Art.32(1)(b) | Security of processing | Editorial | Same topic: Business Continuity (editorial pick) |
| NIS2 | 4.14.3 | Business continuity and disaster recovery plan; Crisis management | Crosswalk | Same topic: Business Continuity |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.11(1)Art.11(4)Art.11(6) | Response and recovery; Response and recovery… | Editorial | Same topic: Business Continuity (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.