NIS2 · 3. Incident handling
3.1
Incident handling policy
frameworkNIS2 Implementing Regulation (EU) 2024/2690
section3. Incident handling
csf 2.0GV.SC-08 RS.MA-01 RS.MA-05 RS.MI-01 RS.MI-02
topicsIncident Response
frameworks7 5 1
Official text · not licensableTitle from ENISA's guidance: Incident handling policy. 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.MA-01RS.MA-02RS.MA-03RS.MA-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved; The incident response plan is executed in coordination with relevant third parties once an incident is declared… | Crosswalk | Same topic: Incident Response4 loosely related (not mappings)GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities Only shares CSF GV.SC-08: related, not a mapping RS.MA-05 The criteria for initiating incident recovery are applied Only shares CSF RS.MA-05: related, not a mapping |
| ISO 27001 | A.5.24A.5.25A.5.26 | Information security incident management planning and preparation; Assessment and decision on information security events… | Crosswalk | Same topic: Incident Response |
| 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 Response1 loosely related (not mappings)CIS 15.4 Ensure Service Provider Contracts Include Security Requirements Only shares CSF GV.SC-08: 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 (editorial pick) |
| PCI DSS | 12.10.112.10.212.10.312.10.4 | Incident response plan ready to activate; Incident response plan reviewed and tested annually… | Crosswalk | Same topic: Incident Response14 loosely related (not mappings)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.2 Written agreements with service providers Only shares CSF GV.SC-08, RS.MA-01: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF GV.SC-08, RS.MA-05: related, not a mapping 1.2.4 Accurate account-data flow diagram maintained Only shares CSF GV.SC-08: related, not a mapping 2.2.1 System configuration standards developed and maintained Only shares CSF RS.MI-02: related, not a mapping 5.3.2 Periodic scans or continuous behavioural analysis Only shares CSF RS.MI-01: related, not a mapping …and 6 more in the downloads |
| CMMC | IR.L2-3.6.1IR.L2-3.6.3 | Incident Handling; Incident Response Testing | Crosswalk | Same topic: Incident Response1 loosely related (not mappings) |
| 800-53 | IR-4IR-8IR-2IR-3 | Incident Handling; Incident Response Plan… | Crosswalk | Same topic: Incident Response7 loosely related (not mappings) |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response12 loosely related (not mappings)§164.314(a)(2)(i) Business Associate Contracts Only shares CSF GV.SC-08, RS.MA-01: related, not a mapping §164.314(a)(2)(iii) Business associate contracts with subcontractors Only shares CSF GV.SC-08, RS.MA-01: related, not a mapping §164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF RS.MA-01: related, not a mapping §164.308(b)(1) Business Associate Contracts and Other Arrangements Only shares CSF GV.SC-08: related, not a mapping §164.308(b)(4) Written Contract or Other Arrangement Only shares CSF GV.SC-08: related, not a mapping §164.314(a) Business Associate Contracts or Other Arrangements Only shares CSF GV.SC-08: 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) |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick) |
| DORA | Art.11(2)(b)Art.17(1)Art.17(3)Art.18(1) | Response and recovery; ICT-related incident management process… | Editorial | Same topic: Incident Response (editorial pick)2 loosely related (not mappings)Art.17(3)(f) ICT-related incident management process Only shares CSF RS.MI-01, RS.MI-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.