NIST Cybersecurity Framework 2.0
RC - Recover

NIST Cybersecurity Framework 2.0 NIST-CSF-RC.RP-04: Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms

Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 57 controls across 26 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 7 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-2(3) Resume Mission and Business Functions
  • CP-6(3) Alternate Storage Site | Accessibility (CP-6(3))
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • IR-3 Incident Response Testing
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))

FedRAMP Moderate · 7 controls

  • CP-10 System Recovery and Reconstitution
  • CP-10(2) System Recovery and Reconstitution | Transaction Recovery (CP-10(2))
  • CP-2(3) Resume Mission and Business Functions
  • CP-6(3) Alternate Storage Site | Accessibility (CP-6(3))
  • CP-7(2) Alternate Processing Site | Accessibility (CP-7(2))
  • IR-3 Incident Response Testing
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))

ASD Strategies to Mitigate Cyber Security Incidents · 3 controls

  • ASD37-34 Regular backups (Essential)
  • ASD37-35 Business continuity and disaster recovery plans (Very Good)
  • ASD37-36 System recovery capabilities (Very Good)

HIPAA Security Rule · 3 controls

ISO 27001:2022 · 3 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 8.14 Redundancy of information processing facilities

NIST SP 800-66 Rev 2 · 3 controls

SOC 2 · 3 controls

  • SOC2-A1.2 A1.2 Environmental protection, backup and recovery infrastructure
  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

Australian Information Security Manual · 2 controls

  • ISM-0734 CISO contribution to continuity and recovery planning
  • ISM-1511 Backups aligned to business criticality

Azure Security Benchmark · 2 controls

  • ASBv3-GS-8 Define and implement backup and recovery strategy
  • BR-1 Ensure regular automated backups

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

  • CFTC-SS-25 Same Day Recovery Time Objective for Critical Entities
  • CFTC-SS-9 Next Business Day Recovery Time Objective

CIS Controls v8 · 2 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-11.4 Establish and Maintain an Isolated Instance of Recovery Data

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 22301:2019 · 2 controls

  • 8.3 Business continuity strategies and solutions
  • 8.4.5 Recovery

ISO 27002:2022 · 2 controls

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

ISO 27701:2019 · 2 controls

  • 6.14 Information security aspects of business continuity management
  • 6.14.1 Information security continuity

NIST SP 800-161 Rev 1 · 2 controls

ACSC Essential Eight · 1 control

  • E8-BACKUP-ML1 Regular Backups (ML1)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-37 Define and Apply a Backup Policy for Critical Components

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-20 Prevention, Adaptation and Return to Normal Operations

C5 (Germany) · 1 control

DORA · 1 control

NIS2 Directive · 1 control

  • Art.21.2.c Business continuity, backup management, disaster recovery and crisis management

NIST SP 800-172 · 1 control

  • 3.14.4e Refresh Systems and Components from a Trusted Baseline

NIST SP 800-53 Rev 5 · 1 control

NIST SP 800-61 Rev. 3 · 1 control

  • RC.RP-04 RC.RP-04 Essential services restored in order and restored systems confirmed with owners and monitored

PCI DSS 4.0 · 1 control

  • 10.7.3 10.7.3 Respond promptly to critical security control failures

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in RC - Recover

You are reading one control. How much of NIST Cybersecurity Framework 2.0 have you already done?

NIST Cybersecurity Framework 2.0 NIST-CSF-RC.RP-04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST Cybersecurity Framework 2.0 your existing evidence covers. Hold ISO 27001:2022 and 73 of 106 NIST Cybersecurity Framework 2.0 controls already carry evidence.

If you hold ISO 27001:202268.9% covered · 33 gapsIf you hold NIST SP 800-53 Rev 567.9% covered · 34 gapsIf you hold C5 (Germany)67% covered · 35 gapsIf you hold FedRAMP Moderate63.2% covered · 39 gapsIf you hold ISO 27002:202258.5% covered · 44 gapsIf you hold CIS Controls v853.8% covered · 49 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 174 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 57 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST Cybersecurity Framework 2.0 controls