NIST Cybersecurity Framework 2.0
RC - Recover

NIST Cybersecurity Framework 2.0 NIST-CSF-RC.CO-03: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders

Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption
  • 5.37 Documented operating procedures

FedRAMP High · 3 controls

  • CP-2 Contingency Plan
  • IR-6 Incident Reporting
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))

FedRAMP Moderate · 3 controls

  • CP-2 Contingency Plan
  • IR-6 Incident Reporting
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))

ISO 22301:2019 · 3 controls

ISO 27002:2022 · 3 controls

  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity

SOC 2 · 3 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • CPS230-P42 APRA Notification of Disruption Outside Tolerance within 24 Hours
  • SEC10-BP01 Identify key personnel and external resources

C5 (Germany) · 1 control

  • C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents

CIS Controls v8 · 1 control

  • CIS-17.6 Define Mechanisms for Communicating During Incident Response

CMMC 2.0 · 1 control

DORA · 1 control

ISO/IEC 42001:2023 · 1 control

  • A.8 Information for interested parties of AI systems

NIS2 Directive · 1 control

  • Art.23.4.c Provide an intermediate report on status when the CSIRT or competent authority requests one
  • RC.CO-3 RC.CO-3: Recovery activities are communicated to internal stakeholders and executive and management teams
  • RC.CO-3 RC.CO-3: Recovery activities are communicated to internal and external stakeholders as well as executive and management teams
  • RC.CO-03 RC.CO-03 Recovery progress shared securely with leadership and suppliers under agreed protocols

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.CO-03 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.

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.

Query this from an agent

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