cm/controlmapping
Sources
NIST CSF 2.0 · Recover (RC)
RC.RP-01

The recovery portion of the incident response plan is executed once initiated from the incident response process

frameworkNIST Cybersecurity Framework 2.0 sectionRecover (RC) topicsRecovery Planning frameworks5 4 1 3

Wrong or missing mapping? Report it

Equivalents of RC.RP-01 in other frameworks
FrameworkRequirementTitleLinkSource / reason
ISO 27001A.5.29A.5.30Information security during disruption; ICT readiness for business continuityCrosswalkSame topic: Recovery Planning
1 loosely related (not mappings)
A.5.26 Response to information security incidents Loosely related
Only shares CSF RC.RP-01: related, not a mapping
CIS v8.1CIS 11.1Establish and Maintain a Data Recovery ProcessEditorialSame topic: Recovery Planning (editorial pick)
SOC 2A1.3CC7.5Testing recovery plan procedures; Recovering from identified security incidentsEditorialSame topic: Recovery Planning (editorial pick)
PCI DSS12.10.1Incident response plan ready to activateCrosswalkSame topic: Recovery Planning
2 loosely related (not mappings)
12.10.2 Incident response plan reviewed and tested annually Loosely related
Only shares CSF RC.RP-01: related, not a mapping
12.10.3 Incident response staff available around the clock Loosely related
Only shares CSF RC.RP-01: related, not a mapping
CMMCIR.L2-3.6.1Incident HandlingLoosely relatedNo mapping. Only shares CSF RC.RP-01: related, not a mapping
800-53CP-2CP-10Contingency Plan; System Recovery and ReconstitutionCrosswalkSame topic: Recovery Planning
2 loosely related (not mappings)
IR-4 Incident Handling Loosely related
Only shares CSF RC.RP-01: related, not a mapping
IR-8 Incident Response Plan Loosely related
Only shares CSF RC.RP-01: related, not a mapping
HIPAA§164.308(a)(7)§164.308(a)(7)(ii)(B)Contingency Plan; Disaster Recovery PlanCrosswalkSame topic: Recovery Planning
3 loosely related (not mappings)
§164.308(a)(6) Security Incident Procedures Loosely related
Only shares CSF RC.RP-01: related, not a mapping
§164.308(a)(6)(ii) Response and Reporting Loosely related
Only shares CSF RC.RP-01: related, not a mapping
§164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Loosely related
Only shares CSF RC.RP-01: related, not a mapping
GDPRArt.32(1)(c)Security of processingEditorialSame topic: Recovery Planning (editorial pick)
NIS24.1Business continuity and disaster recovery planCrosswalkSame topic: Recovery Planning
1 loosely related (not mappings)
4.2 Backup management Loosely related
Only shares CSF RC.RP-01: related, not a mapping
Essential Eight—No requirementNo mapping in our dataNo mapping in our data (Essential Eight links are editorial only).
DORAArt.11(3)Art.12(6)Response and recovery; Backup policies and procedures, restoration and recovery procedures and methodsEditorialSame topic: Recovery Planning (editorial pick)
CPS 234—No requirementNo mapping in our dataNo mapping in our data (CPS 234 is principles-based and its links are editorial).
Cyber Essentials—No requirementNo mapping in our dataNo 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 · Loosely related 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.