ISO 27001 · A.5 Organizational controls
A.5.24
Information security incident management planning and preparation
frameworkISO/IEC 27001:2022
sectionA.5 Organizational controls
csf 2.0DE.AE-02 GV.OV-01 ID.IM-04 RS.MA-02
topicsIncident Response
frameworks7 5 1
Official text · not licensableTitle: Information security incident management planning and preparation. The control text is ISO's copyright; see ISO/IEC 27001:2022.
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 Response2 loosely related (not mappings)DE.AE-02 Potentially adverse events are analyzed to better understand associated activities Only shares CSF DE.AE-02: related, not a mapping GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction Only shares CSF GV.OV-01: 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 Response5 loosely related (not mappings)CIS 13.2 Deploy a Host-Based Intrusion Detection Solution Only shares CSF DE.AE-02: related, not a mapping CIS 13.3 Deploy a Network Intrusion Detection Solution Only shares CSF DE.AE-02: related, not a mapping CIS 13.7 Deploy a Host-Based Intrusion Prevention Solution Only shares CSF DE.AE-02: related, not a mapping CIS 13.8 Deploy a Network Intrusion Prevention Solution Only shares CSF DE.AE-02: related, not a mapping |
| SOC 2 | CC7.3CC7.4P6.6 | Evaluating security events to determine if they are incidents; Responding to identified security incidents… | Editorial | Same topic: Incident Response (editorial pick) ControlMapping editorial: Breach notification to affected parties and regulators: ISO's incident planning and response (A.5.24, A.5.26) plus legal PII obligations (A.5.34). ISO itself sets no notification deadline. 1 loosely related (not mappings) |
| 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)10.4.1 Security event and critical logs reviewed daily Only shares CSF DE.AE-02, RS.MA-02: related, not a mapping 12.10.6 Plan updated from lessons learned and industry changes Only shares CSF GV.OV-01, ID.IM-04: related, not a mapping 10.4.2.1 Review frequency set by targeted risk analysis Only shares CSF DE.AE-02: related, not a mapping 10.7.1 Service providers detect security control failures Only shares CSF GV.OV-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 Response7 loosely related (not mappings) |
| 800-53 | IR-4IR-8IR-2IR-3 | Incident Handling; Incident Response Plan… | Crosswalk | Same topic: Incident Response11 loosely related (not mappings)…and 3 more in the downloads |
| HIPAA | §164.308(a)(6)§164.308(a)(6)(ii) | Security Incident Procedures; Response and Reporting | Crosswalk | Same topic: Incident Response27 loosely related (not mappings)§164.308(a)(1)(ii)(D) Information System Activity Review Only shares CSF DE.AE-02, RS.MA-02: related, not a mapping §164.310(a)(2)(ii) Facility Security Plan Only shares CSF GV.OV-01, ID.IM-04: related, not a mapping …and 19 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) |
| NIS2 | 3.13.5 | Incident handling policy; Incident response | Crosswalk | Same topic: Incident Response |
| Essential Eight | ISM-1819 | Following the identification of a cyber security incident, the cyber security incident… | Editorial | Same topic: Incident Response (editorial pick)4 loosely related (not mappings)ISM-0109 Event logs from workstations are analysed in a timely manner to detect cyber security… Only shares CSF DE.AE-02: related, not a mapping ISM-1228 Cyber security events are analysed in a timely manner to identify cyber security incidents Only shares CSF DE.AE-02: related, not a mapping ISM-1906 Event logs from internet-facing servers are analysed in a timely manner to detect cyber… Only shares CSF DE.AE-02: related, not a mapping ISM-1907 Event logs from non-internet-facing servers are analysed in a timely manner to detect… Only shares CSF DE.AE-02: related, not a mapping |
| 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) |
| 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.