ISO 27001:2022
Organizational controls – ISO 27001:2022

ISO 27001:2022 5.27: Learning from information security incidents

What the organization learns from its information security incidents is to be fed back to strengthen and improve its security controls. Purpose (stated in ISO/IEC 27002:2022): makes future incidents less likely or less harmful. 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.27.

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

What else in your programme already covers this

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

NIST Cybersecurity Framework 2.0 · 6 controls

  • NIST-CSF-GV.OV-01 Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction
  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • NIST-CSF-ID.IM-01 Improvements are identified from evaluations
  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.IM-03 Improvements are identified from execution of operational processes, procedures, and activities
  • NIST-CSF-RS.AN-08 An incident's magnitude is estimated and validated

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-16.3 Perform Root Cause Analysis on Security Vulnerabilities
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CIS-17.8 Conduct Post-Incident Reviews
  • CIS-18.4 Validate Security Measures

COBIT 2019 · 3 controls

  • DSS02.07 DSS02.07 Track status and produce reports
  • DSS03.01 DSS03.01 Identify and classify problems
  • DSS03.02 DSS03.02 Investigate and diagnose problems

HIPAA Security Rule · 3 controls

ISO 27701:2019 · 3 controls

  • 5.8 Improvement
  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements

NIST SP 800-218 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

SOC 2 · 3 controls

  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents

APRA CPS 230 Operational Risk Management · 2 controls

  • CPS230-P31 Remediation of Material Operational Risk Weaknesses
  • CPS230-P45 Annual Update of the Business Continuity Plan

APRA CPS 234 · 2 controls

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

CMMC 2.0 · 2 controls

FedRAMP High · 2 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling

FedRAMP Moderate · 2 controls

  • IR-2 Incident Response Training
  • IR-4 Incident Handling

ISO 22301:2019 · 2 controls

  • 10.1 Nonconformity and corrective action
  • 10.2 Continual improvement

ISO/IEC 42001:2023 · 2 controls

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

NIS2 Directive · 2 controls

  • Art.21.2.b Incident handling
  • Art.23.4.d Submit a final report within one month, and a progress report where the incident is still running

PCI DSS 4.0 · 2 controls

  • 10.7.3 10.7.3 Respond promptly to critical security control failures
  • 12.10.6 12.10.6 Plan evolved from lessons learned and industry developments

ACSC Essential Eight · 1 control

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

AWS Well-Architected Security Pillar · 1 control

  • SEC10-BP08 Establish a framework for learning from incidents

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

Azure Security Benchmark · 1 control

  • ASBv3-IR-7 Post-incident activity - conduct lesson learned and retain evidence

C5 (Germany) · 1 control

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

  • CFTC-SS-21 Remediation of Vulnerabilities and Deficiencies

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

DORA · 1 control

EU AI Act · 1 control

  • EUAI-Art.72 Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems

ISO 27001:2013 · 1 control

  • A.16.1.6 Learning from information security incidents

ISO 27002:2022 · 1 control

  • 5.27 Learning from information security incidents

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.5e Assess Effectiveness of Security Solutions

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

MCP endpointAll ISO 27001:2022 controls