ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.24: Information security incident management planning and preparation 

The organization is to prepare for handling information security incidents by defining, setting up and communicating how incidents are managed and who does what. Purpose (stated in ISO/IEC 27002:2022): makes incident handling fast, effective, consistent and orderly, including how events are communicated. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.24.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 203 controls across 39 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 26 controls

  • AU-5 Response to Audit Logging Process Failures
  • AU-6(3) Correlate Audit Record Repositories
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • CP-2(1) Coordinate with Related Plans
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • RA-5(11) Vulnerability Monitoring and Scanning | Public Disclosure Program (RA-5(11))
  • SA-1 Policy and Procedures
  • SA-2 Allocation of Resources
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))
  • SI-4(5) System-Generated Alerts
  • SI-5 Security Alerts, Advisories, and Directives
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 26 controls

  • AU-5 Response to Audit Logging Process Failures
  • AU-6(3) Correlate Audit Record Repositories
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • CP-2(1) Coordinate with Related Plans
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • IR-3 Incident Response Testing
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-5 Incident Monitoring
  • IR-6 Incident Reporting
  • IR-6(1) Automated Reporting
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan
  • IR-9 Information Spillage Response (IR-9)
  • IR-9(3) Information Spillage Response | Post-spill Operations (IR-9(3))
  • IR-9(4) Information Spillage Response | Exposure to Unauthorized Personnel (IR-9(4))
  • RA-5(11) Vulnerability Monitoring and Scanning | Public Disclosure Program (RA-5(11))
  • SA-1 Policy and Procedures
  • SA-2 Allocation of Resources
  • SI-4(16) System Monitoring | Correlate Monitoring Information (SI-4(16))
  • SI-4(5) System-Generated Alerts
  • SI-5 Security Alerts, Advisories, and Directives
  • SI-7(7) Integration of Detection and Response

NIST SP 800-53 Rev 5 · 19 controls

NIST Cybersecurity Framework 2.0 · 16 controls

  • NIST-CSF-DE.AE-04 The estimated impact and scope of adverse events are understood
  • NIST-CSF-DE.AE-06 Information on adverse events is provided to authorized staff and tools
  • NIST-CSF-GV.RM-05 Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third parties
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
  • NIST-CSF-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
  • NIST-CSF-ID.IM-04 Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved
  • NIST-CSF-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • NIST-CSF-PR.IR-03 Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • NIST-CSF-RC.RP-01 The recovery portion of the incident response plan is executed once initiated from the incident response process
  • NIST-CSF-RC.RP-02 Recovery actions are selected, scoped, prioritized, and performed
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared
  • NIST-CSF-RS.MA-03 Incidents are categorized and prioritized
  • NIST-CSF-RS.MA-04 Incidents are escalated or elevated as needed
  • NIST-CSF-RS.MA-05 The criteria for initiating incident recovery are applied

CIS Controls v8 · 12 controls

  • CIS-11.1 Establish and Maintain a Data Recovery Process
  • CIS-14.7 Train Workforce on How to Identify and Report if Their Enterprise Assets are Missing Security Updates
  • CIS-17.1 Designate Personnel to Manage Incident Handling
  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.5 Assign Key Roles and Responsibilities
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response
  • CIS-17.7 Conduct Routine Incident Response Exercises
  • CIS-18.1 Establish and Maintain a Penetration Testing Program
  • CIS-18.4 Validate Security Measures
  • CIS-7.2 Establish and Maintain a Remediation Process

PCI DSS 4.0 · 12 controls

  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 10.7.2 10.7.2 Detect and alert on critical security control failures
  • 10.7.3 10.7.3 Respond promptly to critical security control failures
  • 11.5.1 11.5.1 IDS/IPS monitoring of CDE traffic
  • 11.5.1.1 11.5.1.1 Service providers detect covert malware channels
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • 12.10.3 12.10.3 Incident response personnel available 24/7
  • 12.10.4.1 12.10.4.1 Responder training frequency set by targeted risk analysis
  • 12.10.5 12.10.5 Plan covers alerts from security monitoring systems
  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations
  • 5.4.1 5.4.1 Mechanisms detect and protect against phishing

ISO 22301:2019 · 9 controls

  • 6.1 Actions to address risks and opportunities
  • 7.4 Communication
  • 8.2.2 Business impact analysis
  • 8.4 Business continuity plans and procedures
  • 8.4.1 General
  • 8.4.2 Response structure
  • 8.4.3 Warning and communication
  • 8.4.4 Business continuity plans
  • 8.5 Exercise programme

SOC 2 · 8 controls

  • SOC2-A1.3 A1.3 Testing recovery plan procedures
  • SOC2-CC3.3 CC3.3 Considering fraud risk (COSO principle 8)
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-P6.3 P6.3 Record of unauthorised disclosures and breaches
  • SOC2-P6.6 P6.6 Notifying breaches and incidents
  • SOC2-P8.1 P8.1 Inquiries, complaints, disputes and compliance monitoring

AWS Well-Architected Security Pillar · 6 controls

CMMC 2.0 · 6 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 4 controls

DORA · 4 controls

HIPAA Security Rule · 4 controls

NIST SP 800-171 Rev 3 · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

APRA CPS 234 · 3 controls

  • CPS234-32 Annual Review and Testing of Response Plans
  • CPS234-P24 Information Security Response Plans
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

Azure Security Benchmark · 3 controls

  • ASBv3-GS-7 Define and implement logging, threat detection and incident response strategy
  • ASBv3-IR-1 Preparation - update incident response plan and handling process
  • ASBv3-IR-2 Preparation - setup incident notification

COBIT 2019 · 3 controls

  • APO12.06 APO12.06 Respond to risk
  • DSS02.01 DSS02.01 Define classification schemes for incidents and service requests
  • DSS02.06 DSS02.06 Close service requests and incidents

EU AI Act · 3 controls

ISO 27002:2022 · 3 controls

  • 5.24 Information security incident management planning and preparation
  • 5.29 Information security during disruption
  • 6.8 Information security event reporting

ISO 27701:2019 · 3 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements
  • 7.2.5 Privacy impact assessment

ISO/IEC 42001:2023 · 3 controls

  • A.5.4 Assessing AI system impact on individuals or groups of individuals
  • A.8.3 External reporting
  • A.8.4 Communication of incidents

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

ISO/IEC 29100:2024 · 2 controls

  • 29100-6.10 Information security
  • ISO29100-5.10.10 Information Security

NIS2 Directive · 2 controls

  • Art.21.2.b Incident handling
  • Art.23.1 Notify significant incidents to the CSIRT or competent authority, and warn affected service recipients

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.6.1e Establish Security Operations Center (SOC)
  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

ACSC Essential Eight · 1 control

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-40 Define a Security Incident Management Procedure

APPI · 1 control

  • APPI-A26 Report of Leakage to the Commission and Notification to the Person

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-27 Identification and Escalation of Incidents and Near Misses

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-28 Continuous incident detection and response (Excellent)

Australia Consumer Data Right - Banking (CDR) · 1 control

Australia My Health Records Act 2012 · 1 control

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

  • AEO-12 Crisis Management and Incident Recovery

C5 (Germany) · 1 control

  • C5-SIM-01 Policy for security incident management

GDPR · 1 control

  • GDPR-Art.33 Notification of a personal data breach to the supervisory authority

ISO 27001:2013 · 1 control

  • A.16.1.1 Responsibilities and procedures

NIST SP 800-218 · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Organizational controls – ISO 27001:2022

You are reading one control. How much of ISO 27001:2022 have you already done?

ISO 27001:2022 5.24 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gapsIf you hold ISO 27001:201383.9% covered · 15 gapsIf you hold FedRAMP Moderate80.6% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gapsIf you hold C5 (Germany)69.9% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 203 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ISO 27001:2022 controls