NIST Cybersecurity Framework 2.0 NIST-CSF-RC.CO-04: Public updates on incident recovery are shared using approved methods and messaging

What else in your programme already covers this

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

Australian Information Security Manual · 2 controls

ISM-1880 Reporting incidents involving customer data
ISM-1881 Reporting incidents not involving customer data

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

CCM-BCR-07 Communication
CCM-SEF-07 Security Breach Notification

ISO 22301:2019 · 2 controls

7.4 Communication
8.4.3 Warning and communication

ISO 27001:2022 · 2 controls

5.26 Response to information security incidents
5.5 Contact with authorities

ISO 27701:2019 · 2 controls

5.5.4 Communication
6.13.1 Management of information security incidents and improvements

NIST Cybersecurity Framework 1.0 · 2 controls

RC.CO-1 RC.CO-1: Public relations are managed
RC.CO-2 RC.CO-2: Reputation after an event is repaired

NIST Cybersecurity Framework 1.1 · 2 controls

RC.CO-1 RC.CO-1: Public relations are managed
RC.CO-2 RC.CO-2: Reputation is repaired after an incident

ASIC Cyber Resilience Good Practices · 1 control

ASIC-CR-RR-5 Stakeholder communication plan

C5 (Germany) · 1 control

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

CMMC 2.0 · 1 control

AC.L2-3.1.22 Control Public Information

DORA · 1 control

DORA-Art.14 Communication

FedRAMP High · 1 control

IR-6 Incident Reporting

HIPAA Security Rule · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

ISO 27002:2022 · 1 control

5.26 Response to information security incidents

NIS2 Directive · 1 control

Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

NIST SP 800-53 Rev 5 · 1 control

NIST800-IR-6 IR-6 Incident Reporting

NIST SP 800-61 Rev. 3 · 1 control

RC.CO-04 RC.CO-04 Public recovery updates follow breach procedures and explain prevention steps

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

SOC 2 · 1 control

SOC2-P6.6 P6.6 Notifying breaches and incidents

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.

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-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 gaps If you hold NIST SP 800-53 Rev 567.9% covered · 34 gaps If you hold C5 (Germany)67% covered · 35 gaps If you hold FedRAMP Moderate63.2% covered · 39 gaps If you hold ISO 27002:202258.5% covered · 44 gaps If 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 each Browse the graph free