RC.CO-03 RC · Recover · RC.CO Incident Recovery Communication

RC.CO-03 — Recovery communication to stakeholders

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

Also written as RC-CO-03, RC.CO-3, CSF 2.0 RC.CO-03, NIST CSF RC.CO.

What NIST CSF RC.CO-03 means

RC.CO-03 is one of 8 subcategories in the Recover (RC) function, under the Incident Recovery Communication category (RC.CO). The Core states: “Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders.” Recover outcomes are the least frequently tested in practice and the most commonly assumed — restoration evidence from a real test, not a backup job that reports success, is what demonstrates the outcome.

Evidence that supports RC.CO-03

To demonstrate this outcome in an assessment or audit, gather artefacts such as:

  • Recovery progress updates to internal and external stakeholders
  • Customer communications on service restoration
  • Regulator updates where required

ISO 27001 mapping

RC.CO-03 has no direct one-to-one ISO 27001:2022 Annex A equivalent — it is a governance or process outcome that ISO 27001 addresses at the management-system level (Clauses 4–10) rather than through a specific Annex A control. Treat it as its own requirement in your CSF profile.

Map RC.CO-03 to ISO 27001 & SOC 2 →
Crosswalk this subcategory in the Control Mapper & Gap Assessment.
Document the risk →
Record treatment for gaps against RC.CO-03 in the Risk Register.

Other Incident Recovery Communication subcategories

RC.CO-04 Public recovery updates

All 8 Recover subcategories →

Frequently asked questions

Is NIST CSF RC.CO-03 mandatory?

No. CSF 2.0 is a voluntary framework of outcomes rather than a set of requirements, and there is no certification against it. RC.CO-03 becomes binding only when something else makes it so — a contract, a regulator that references CSF, or your own Target Profile. That is the practical difference between CSF and an auditable standard like ISO 27001 or SOC 2.

How is RC.CO-03 assessed?

Through profiles rather than pass/fail testing. You record how fully the outcome is achieved today in a Current Profile, state where it needs to be in a Target Profile, and the gap between them becomes your action plan. Implementation Tiers (Partial, Risk Informed, Repeatable, Adaptive) describe how rigorous your governance around the outcome is, not whether you have met it.

Who owns RC.CO-03?

The Recover function is normally owned by the security or IT function, but RC.CO-03 still needs a specific named owner. Assessors treat an outcome with no owner as not achieved regardless of the tooling behind it, so record ownership in your profile alongside the assessment.