CIS v8.1 · 17. Incident Response Management
CIS 17.6
Define Mechanisms for Communicating During Incident Response
frameworkCIS Controls v8.1
section17. Incident Response Management
csf 2.0RC.CO-04 RS.CO-03
topicsCommunication, Comms & Restore
frameworks5 4 2
Official text · not licensableSafeguard title © CIS (CC BY-NC-ND 4.0). See CIS Controls v8.1 for details.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | RC.CO-03RC.CO-04RC.RP-05RS.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders; Public updates on incident recovery are shared using approved methods and messaging… | Crosswalk | Same topic: Comms & Restore, Communication |
| ISO 27001 | A.5.26Clause 7.4A.5.6 | Response to information security incidents; Communication… | Crosswalk | Same topic: Comms & Restore, Communication |
| SOC 2 | CC2.3CC7.5 | Communication with external parties; Recovering from identified security incidents | Editorial | Same topic: Communication, Comms & Restore (editorial pick) |
| PCI DSS | 12.10.112.10.312.8.212.8.4 | Incident response plan ready to activate; Incident response staff available around the clock… | No mapping. Only shares CSF RC.CO-04, RS.CO-03: related, not a mapping+1 more loosely related (not mappings)12.10.6 Plan updated from lessons learned and industry changes Only shares CSF RS.CO-03: related, not a mapping | |
| CMMC | IR.L2-3.6.2 | Incident Reporting | Crosswalk | Same topic: Communication, Comms & Restore1 loosely related (not mappings) |
| 800-53 | CP-10IR-6IR-7 | System Recovery and Reconstitution; Incident Reporting… | Crosswalk | Same topic: Comms & Restore, Communication4 loosely related (not mappings) |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii)§164.308(a)(7)§164.308(a)(7)(ii)(B) | Security Incident Procedures; Response and Reporting… | No mapping. Only shares CSF RC.CO-04, RS.CO-03: related, not a mapping+9 more loosely related (not mappings)§164.308(a)(7)(ii)(C) Emergency Mode Operation Plan Only shares CSF RC.CO-04: related, not a mapping §164.308(a)(7)(ii)(D) Testing and Revision Procedure Only shares CSF RC.CO-04: related, not a mapping §164.308(a)(7)(ii)(E) Applications and Data Criticality Analysis Only shares CSF RC.CO-04: related, not a mapping …and 5 more in the downloads | |
| GDPR | Art.34(1) | Communication of a personal data breach to the data subject | Editorial | Same topic: Comms & Restore (editorial pick) |
| NIS2 | 4.3 | Crisis management | Crosswalk | Same topic: Communication, Comms & Restore1 loosely related (not mappings) |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.11(2)(e)Art.11(7)Art.14(1)Art.14(2)Art.17(3)(d) | Response and recovery; Response and recovery… | Editorial | Same topic: Comms & Restore, Communication (editorial pick) |
| CPS 234 | Para 25 | Response plans cover all stages and escalation | Editorial | Same topic: Communication (editorial pick) |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.