RC.CO-04
Public updates on incident recovery are shared using approved methods and messaging
Implementation examples
- Ex1: Follow the organization's breach notification procedures for recovering from a data breach incident
- Ex2: Explain the steps being taken to recover from the incident and to prevent a recurrence
Mapped NIST 800-53 r5 controls (2)
Mapped CWE weaknesses (1)
Hover any chip for the human-reviewed coverage assessment in each direction. ← = the CWE covers this subcategory; → = this subcategory covers the CWE. F / M / P = full, mostly, partial.
All informative references (28)
- AI-SOC: AI-SOC-30
- AI-SOC: AI-SOC-12
- CIS Controls v8.0: 17.2
- CIS Controls v8.0: 17.6
- CIS Controls v8.1: 17.2
- CIS Controls v8.1: 17.6
- CRI Profile v2.0: RC.CO-04
- CRI Profile v2.0: RC.CO-04.01
- CSF v1.1: RC.CO-1
- CSF v1.1: RS.CO-2
- ISO/IEC 27001:2022: Mandatory Clause: 7.4
- ISO/IEC 27001:2022: Annex A Controls: None
- NICE Framework: OG-WRL-006
- NICE Framework: OG-WRL-007
- NICE Framework: OG-WRL-008
- NICE Framework: OG-WRL-010
- NICE Framework: OG-WRL-015
- NICE Framework: PD-WRL-003
- OWASP Top 10 LLM Applications: LLM02-2025
- PCI DSS: 12.10.1
- PCI DSS: 12.10.3
- SCF: IRO-16
- SP 800-171 Rev 3: 03.06.01
- SP 800-221A: GV.CO-1
- SP 800-53 Rev 5.1.1: CP-02
- SP 800-53 Rev 5.1.1: IR-04
- SP 800-53 Rev 5.2.0: CP-02
- SP 800-53 Rev 5.2.0: IR-04
Source: NIST Cybersecurity Framework 2.0 · CSF 2.0 → 800-53 mappings sourced from NIST Cybersecurity & Privacy Reference Tool (CPRT) · US government work — attribution requested per NIST Open License Terms. Direct CSF→CWE/CVE cross-references will be added in a Phase B LLM-authored mapping pass (not yet rendered).