NIS2 · 3. Incident handling
3.5
Incident response
frameworkNIS2 Implementing Regulation (EU) 2024/2690
section3. Incident handling
csf 2.0RC.CO-03 RC.CO-04 RS.AN-03 RS.CO-02 RS.CO-03 RS.MA-01 RS.MA-02 RS.MA-03 RS.MA-04 RS.MI-01 RS.MI-02
topicsIncident Response, Forensics, Mitigation
frameworks7 5 1
Official text · not licensableTitle from ENISA's guidance: Incident response. See the Annex to Implementing Regulation (EU) 2024/2690 for the legal text.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | ID.IM-04RS.AN-03RS.AN-06RS.AN-07RS.MA-01RS.MA-02RS.MA-03RS.MA-04RS.MI-01RS.MI-02 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved; Analysis is performed to establish what has taken place during an incident and the root cause of the incident… | Crosswalk | Same topic: Incident Response, Forensics, Mitigation4 loosely related (not mappings)RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders Only shares CSF RC.CO-03: related, not a mapping RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging Only shares CSF RC.CO-04: related, not a mapping RS.CO-02 Internal and external stakeholders are notified of incidents Only shares CSF RS.CO-02: related, not a mapping RS.CO-03 Information is shared with designated internal and external stakeholders Only shares CSF RS.CO-03: related, not a mapping |
| ISO 27001 | A.5.24A.5.25A.5.26A.5.28 | Information security incident management planning and preparation; Assessment and decision on information security events… | Crosswalk | Same topic: Incident Response, Mitigation, Forensics4 loosely related (not mappings)Clause 7.4 Communication Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping A.5.27 Learning from information security incidents Only shares CSF RS.AN-03, RS.MA-01, RS.MA-02: related, not a mapping |
| CIS v8.1 | CIS 17.4CIS 17.1CIS 17.5CIS 17.7CIS 17.9 | Establish and Maintain an Incident Response Process; Designate Personnel to Manage Incident Handling… | Crosswalk | Same topic: Incident Response4 loosely related (not mappings)CIS 17.2 Establish and Maintain Contact Information for Reporting Security Incidents Only shares CSF RC.CO-04, RS.CO-02, RS.CO-03: related, not a mapping CIS 17.6 Define Mechanisms for Communicating During Incident Response Only shares CSF RC.CO-04, RS.CO-03: related, not a mapping CIS 17.3 Establish and Maintain an Enterprise Process for Reporting Incidents Only shares CSF RS.CO-02: related, not a mapping |
| SOC 2 | CC7.3CC7.4 | Evaluating security events to determine if they are incidents; Responding to identified security incidents | Editorial | Same topic: Incident Response, Forensics, Mitigation (editorial pick) |
| PCI DSS | 10.3.212.10.112.10.212.10.312.10.4 | Logs protected from modification; Incident response plan ready to activate… | Crosswalk | Same topic: Forensics, Incident Response, Mitigation14 loosely related (not mappings)12.8.2 Written agreements with service providers Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01: related, not a mapping 10.4.1 Security event and critical logs reviewed daily Only shares CSF RS.AN-03, RS.MA-02, RS.MA-03: related, not a mapping 5.2.2 Anti-malware detects, removes or contains known malware Only shares CSF RS.MI-01, RS.MI-02: related, not a mapping 12.8.4 Service provider compliance monitored annually Only shares CSF RC.CO-03, RS.CO-03: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF RS.CO-03, RS.MA-03: related, not a mapping 2.2.1 System configuration standards developed and maintained Only shares CSF RS.MI-02: related, not a mapping …and 6 more in the downloads |
| CMMC | AU.L2-3.3.6IR.L2-3.6.1IR.L2-3.6.3 | Reduction & Reporting; Incident Handling… | Crosswalk | Same topic: Forensics, Incident Response, Mitigation1 loosely related (not mappings)IR.L2-3.6.2 Incident Reporting Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01…: related, not a mapping |
| 800-53 | AU-7IR-4IR-8SI-2(7)IR-2IR-3 | Audit Record Reduction and Report Generation; Incident Handling… | Crosswalk | Same topic: Forensics, Incident Response, Mitigation6 loosely related (not mappings)IR-6 Incident Reporting Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01…: related, not a mapping IR-7 Incident Response Assistance Only shares CSF RS.CO-02, RS.CO-03, RS.MA-01, RS.MA-04: related, not a mapping SR-8 Notification Agreements Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01: related, not a mapping SR-3 Supply Chain Controls and Processes Only shares CSF RS.CO-02, RS.CO-03, RS.MA-01: related, not a mapping |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response, Mitigation12 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RC.CO-03, RS.AN-03, RS.CO-02, RS.CO-03…: related, not a mapping §164.314(a)(2)(i) Business Associate Contracts Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01…: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01…: related, not a mapping §164.314(b)(2)(iv) Group Health Plan Implementation Specification Only shares CSF RC.CO-03, RS.CO-02, RS.CO-03, RS.MA-01…: related, not a mapping §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 …and 4 more in the downloads |
| GDPR | Art.33(1)Art.33(5) | Notification of a personal data breach to the supervisory authority; Notification of a personal data breach to the supervisory authority | Editorial | Same topic: Incident Response (editorial pick)1 loosely related (not mappings)Art.34(1) Communication of a personal data breach to the data subject Only shares CSF RC.CO-03, RC.CO-04, RS.CO-02: related, not a mapping |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick)2 loosely related (not mappings)ISM-0123 Cyber security incidents are reported to the chief information security officer, or one… Only shares CSF RS.CO-02: related, not a mapping ISM-0140 Cyber security incidents are reported to ASD as soon as possible after they occur or… Only shares CSF RS.CO-02: related, not a mapping |
| DORA | Art.11(2)(b)Art.11(2)(c)Art.13(2)Art.17(1)Art.17(2)Art.17(3)Art.17(3)(f)Art.18(1) | Response and recovery; Response and recovery… | Editorial | Same topic: Incident Response, Mitigation, Forensics (editorial pick)8 loosely related (not mappings)Art.17(3)(d) ICT-related incident management process Only shares CSF RS.CO-03: related, not a mapping Art.19(1) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Only shares CSF RS.CO-02: related, not a mapping Art.19(3) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Only shares CSF RS.CO-02: related, not a mapping Art.19(4) Reporting of major ICT-related incidents and voluntary notification of significant cyber threats Only shares CSF RS.CO-02: related, not a mapping |
| CPS 234 | Para 23Para 24Para 25Para 26 | Detect and respond to incidents in a timely manner; Maintain information security response plans… | Editorial | Same topic: Incident Response (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.