ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.26: Response to information security incidents

Incidents are to be handled following the documented response procedures. Purpose (stated in ISO/IEC 27002:2022): ensures incidents are responded to efficiently and effectively. 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.26.

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

What else in your programme already covers this

This control maps to 134 controls across 36 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 · 17 controls

  • AC-2(13) Disable Accounts for High-Risk Individuals
  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • 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(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • 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))
  • SI-7(7) Integration of Detection and Response

FedRAMP Moderate · 17 controls

  • AC-2(13) Disable Accounts for High-Risk Individuals
  • AU-5 Response to Audit Logging Process Failures
  • IR-1 Policy and Procedures
  • IR-2 Incident Response Training
  • 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(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • 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))
  • SI-7(7) Integration of Detection and Response

NIST Cybersecurity Framework 2.0 · 15 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-ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • NIST-CSF-RC.CO-04 Public updates on incident recovery are shared using approved methods and messaging
  • 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.AN-03 Analysis is performed to establish what has taken place during an incident and the root cause of the incident
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
  • 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-04 Incidents are escalated or elevated as needed
  • NIST-CSF-RS.MA-05 The criteria for initiating incident recovery are applied
  • NIST-CSF-RS.MI-01 Incidents are contained
  • NIST-CSF-RS.MI-02 Incidents are eradicated

NIST SP 800-53 Rev 5 · 11 controls

PCI DSS 4.0 · 8 controls

  • 10.4.3 10.4.3 Exceptions and anomalies from log review addressed
  • 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
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.3 12.10.3 Incident response personnel available 24/7
  • 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

CIS Controls v8 · 6 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response
  • CIS-17.7 Conduct Routine Incident Response Exercises
  • CIS-17.8 Conduct Post-Incident Reviews

ISO 22301:2019 · 5 controls

  • 10.2 Continual improvement
  • 8.4.2 Response structure
  • 8.4.3 Warning and communication
  • 8.4.4 Business continuity plans
  • 8.5 Exercise programme

AWS Well-Architected Security Pillar · 4 controls

SOC 2 · 4 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • 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

C5 (Germany) · 3 controls

  • C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents
  • C5-SIM-02 Processing of security incidents
  • C5-SIM-03 Documentation and reporting of security incidents

CMMC 2.0 · 3 controls

COBIT 2019 · 3 controls

  • APO12.06 APO12.06 Respond to risk
  • DSS02.04 DSS02.04 Investigate, diagnose and allocate incidents
  • DSS02.05 DSS02.05 Resolve and recover from incidents

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

DORA · 3 controls

HIPAA Security Rule · 3 controls

ISO 27701:2019 · 3 controls

  • 5.8.1 Nonconformity and corrective action
  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

Azure Security Benchmark · 2 controls

  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • ASBv3-IR-6 Containment, eradication and recovery - automate the incident handling

EU AI Act · 2 controls

ISO 27002:2022 · 2 controls

  • 5.26 Response to information security incidents
  • 6.8 Information security event reporting

ISO/IEC 42001:2023 · 2 controls

  • 10.2 Nonconformity and corrective action
  • A.8.4 Communication of incidents

NIST SP 800-171 Rev 3 · 2 controls

  • 03.06.01 Incident Handling
  • 03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-66 Rev 2 · 2 controls

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

APRA CPS 234 · 1 control

  • CPS234-P25 Response Plan Content and Escalation Mechanisms

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

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-16 Security Incident Response Plan and Testing

GDPR · 1 control

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

ISO 27001:2013 · 1 control

  • A.16.1.5 Response to information security incidents

NIS2 Directive · 1 control

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

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.26 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 134 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ISO 27001:2022 controls