Skip to content
Organisational controls
ISO 27001A.5.27

ISO 27001 Annex A 5.27 Learning from information security incidents

What it says

Knowledge gained from information security incidents shall be used to strengthen and improve the information security controls.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Use knowledge gained from information security incidents to strengthen and improve your information security controls, so lessons lead to actual changes.

Your organisation must use the knowledge gained from information security incidents to strengthen and improve its information security controls. Writing a lesson down is not enough: it has to feed into a control where the incident shows one is weak or missing. Knowledge includes what happened, why, how the response went and patterns across incidents, such as repeated causes. Controls include technical settings, procedures and the incident management process itself.

Why it matters

If lessons stay in a report nobody acts on, the same phishing route, missed patch or slow escalation can cause or worsen the next incident. Feeding them into controls makes a repeat less likely and its consequences smaller.

How to implement

  1. Review each closed incident, or prepare a review format if you have had none.

    Work out the root cause, which controls failed, helped or were missing, and how the response went. Match the effort to how serious it was, from a short note to a full review. Where a supplier ran the affected service, request its root cause report.

  2. Turn each finding into a tracked change to a control.

    Record what will change, such as a setting, rule or procedure, with an owner, a due date and the incident it came from. Use the same tracker as your other security work, so actions stay visible.

  3. Use patterns to update your risk assessment.

    Track incident types, volumes and costs. When a type recurs or proves serious, update the risk assessment and decide which controls to add or adjust.

  4. Update the incident process and procedures where the response fell short.

    Change the plan, scenarios and steps (Annex A 5.24 and Annex A 5.26). Where people's actions were part of the cause, add a real example, with sensitive details removed, to your awareness material (Annex A 6.3).

  5. Test each change, then close the action.

    Show the change works, for example by repeating the attack path in an agreed test (Annex A 8.34) or re-running the failed step, and keep the result. Where the weak control sits with a supplier you cannot direct, raise it in your supplier reviews (Annex A 5.22) and add your own safeguard.

Keep it running

Track improvements from incidents until they close, and review incident types, volumes and costs for patterns. Treat a repeat incident as a prompt to check whether the earlier fix worked.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The incident list, matched to post-incident reviews.

    Look at

    Whether any closed incident has no recorded review, and whether the effort matches how serious it was.

    Good evidence

    Each closed incident has a recorded review that names what was learned, or a recorded reason there was nothing to learn.

  2. Check 2 of 4What an auditor asks for

    Ask for

    Improvement actions from a sample of reviews, with the changed setting, rule or procedure for each.

    Look at

    The live setting or current document, not just the action's status in the tracker.

    Good evidence

    Each action marked closed matches a change that is actually in place, and each open one has an owner and a due date.

  3. Check 3 of 4What an auditor asks for

    Ask for

    Incident figures by type and the current risk assessment.

    Look at

    Whether recurring or serious incident types show up in the risk assessment and led to decisions on controls.

    Good evidence

    Recurring and serious types appear in the risk assessment, with a decision on which controls to add or adjust.

  4. Check 4 of 4What an auditor asks for

    Ask for

    Any two incidents with the same cause, with both reviews.

    Look at

    Whether the first produced a change to a control, and why that change did not prevent the second.

    Good evidence

    The second review examines the earlier fix and records why it failed or fell short, with a stronger action as a result. If no cause has repeated, the recorded root causes show that.

Mappings

Closest match in ASD Essentials for enterprise IT: IT.RES-04.1, Perform post-incident reviews to identify security gaps behind each incident stage, which this control covers in full and more.

ASD ISM

ASD Information Security Manual: 2 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.