CIS v8.1 · 17. Incident Response Management
CIS 17.8
Conduct Post-Incident Reviews
frameworkCIS Controls v8.1
section17. Incident Response Management
csf 2.0ID.IM-03 RC.RP-06 RS.AN-03
topicsLessons Learned
frameworks0 9 3
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 | ID.IM-03RC.RP-06 | Improvements are identified from execution of operational processes, procedures, and activities; The end of incident recovery is declared based on criteria, and incident-related documentation is completed | Editorial | Same topic: Lessons Learned (editorial pick)1 loosely related (not mappings)RS.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident Only shares CSF RS.AN-03: related, not a mapping |
| ISO 27001 | A.5.27Clause 10.1 | Learning from information security incidents; Continual improvement | Editorial | Same topic: Lessons Learned (editorial pick) |
| SOC 2 | CC7.5 | Recovering from identified security incidents | Editorial | Same topic: Lessons Learned (editorial pick)1 loosely related (not mappings) |
| PCI DSS | 12.10.6 | Plan updated from lessons learned and industry changes | Editorial | Same topic: Lessons Learned (editorial pick)6 loosely related (not mappings)10.2.2 Log entries record who, what, when, where and outcome Only shares CSF RS.AN-03: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF RS.AN-03: related, not a mapping 10.5.1 Audit logs retained 12 months, three immediately available Only shares CSF RC.RP-06: related, not a mapping 12.10.2 Incident response plan reviewed and tested annually Only shares CSF RC.RP-06: related, not a mapping |
| CMMC | IR.L2-3.6.1 | Incident Handling | Editorial | Same topic: Lessons Learned (editorial pick)1 loosely related (not mappings) |
| 800-53 | IR-4 | Incident Handling | Editorial | Same topic: Lessons Learned (editorial pick) |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii)§164.308(a)(1)(ii)(D)§164.312(b) | Security Incident Procedures; Response and Reporting… | No mapping. Only shares CSF ID.IM-03, RC.RP-06, RS.AN-03: related, not a mapping | |
| GDPR | — | No requirement | No mapping in our data | No mapping in our data (only GDPR's security articles are mapped, editorially). |
| NIS2 | 3.6 | Post-incident reviews | Editorial | Same topic: Lessons Learned (editorial pick)1 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.13(2)Art.13(3) | Learning and evolving; Learning and evolving | Editorial | Same topic: Lessons Learned (editorial pick)1 loosely related (not mappings) |
| CPS 234 | Para 25 | Response plans cover all stages and escalation | Editorial | Same topic: Lessons Learned (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.