Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, individual lessons, and BMC Cyber Challenge activities.

NIST CSF Category profileIntermediate

Incident Recovery Communication (RC.CO) — NIST CSF 2.0 Category

Use RC.CO to manage recovery status, stakeholder expectations, public updates, and coordinated transition within the Recover Function.

Framework mapping

NIST Cybersecurity Framework 2.0

CSF 2.0
CategoryRC.CO — Incident Recovery Communication
FunctionRC — RecoverCategoryRC.CO — Incident Recovery Communication
Official CSF Core outcome

Restoration activities are coordinated with internal and external parties.

CSF outcomes describe what an organization may seek to achieve. They do not prescribe one implementation or turn the Core into a universal checklist.

Category outcome

NIST CSF 2.0 places Incident Recovery Communication (RC.CO) within the Recover Function. The official Category outcome is: “Restoration activities are coordinated with internal and external parties.”

This Category provides a structured way to address recovery status, stakeholder expectations, public updates, and coordinated transition. It groups related Subcategory outcomes without prescribing a specific technology, organizational model, or implementation sequence.

What this means in practice

A credible Incident Recovery Communication capability connects policy and risk decisions to repeatable operating practices. The organization should define scope, ownership, expected outcomes, evidence, exceptions, and reassessment triggers.

Implementation should be proportionate to mission needs, legal and contractual obligations, threat exposure, business impact, and the organization’s risk appetite. The same Category may be implemented differently across systems and business contexts.

Implementation priorities

The following priorities translate the Category into an operating capability. They are starting points for design and governance, not a replacement for architecture, procedures, or risk analysis.

  • Identify internal and external audiences that require recovery information.
  • Define status cadence, approval authority, channels, and content standards.
  • Communicate service availability, limitations, dependencies, and expected next steps.
  • Coordinate public updates with legal, privacy, customer, supplier, and operational teams.
  • Record commitments and update them as recovery evidence changes.

Evidence and measurement

Evidence should show that the Category’s outcomes are achieved in the intended scope, remain effective, and are reviewed when conditions change. A policy, tool purchase, or completed checklist is not sufficient by itself.

  • Recovery communication plan and contact rosters
  • Status reports and stakeholder briefings
  • Public updates and approval records
  • Customer, supplier, regulator, and insurer communications
  • Communication timeline and commitment tracking

Subcategories within RC.CO

This Category contains 2 CSF 2.0 Subcategory outcomes. Each outcome has a dedicated Bare Metal Cyber profile with the official NIST statement and original implementation guidance.

  • RC.CO-03 — Communicate Recovery Progress: Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • RC.CO-04 — Share Public Recovery Updates: Public updates on incident recovery are shared using approved methods and messaging

Using this Category in Current and Target Profiles

For a Current Profile, record which Subcategory outcomes are achieved, the scope of the assessment, and the evidence supporting the judgment. For a Target Profile, select the outcomes needed to meet risk management objectives and describe the target conditions.

Prioritize the resulting gaps by mission consequence, risk exposure, dependencies, obligations, implementation effort, and the value of the improvement. Record the owner and the evidence that will demonstrate closure.

Common failure modes

The following conditions can create the appearance of coverage without reliable outcome achievement. Treat them as hypotheses to test during assessments, exercises, and operational reviews.

  • Status reports overstate certainty or omit service limitations.
  • Different audiences receive inconsistent recovery information.
  • Public statements are not synchronized with technical evidence.
  • Recovery commitments are made without operational ownership or validation.

Source, scope, and attribution

The Category identifier, name, description, and Subcategory outcomes are from NIST CSWP 29. Bare Metal Cyber’s implementation, evidence, failure-mode, and Profile guidance is original educational material.

The CSF describes outcomes, not mandatory implementation steps. Use NIST’s current online Implementation Examples and Informative References when selecting practices and controls for a specific environment.

Certification relevance

This subject appears in or supports the following certification bodies of knowledge:

NIST CSF 2.0CompTIA Security+ISC2 CISSPGIAC GSEC

Authoritative sources