A.5 Organizational controls

A.5.24 Information security incident management planning and preparation

Not mandatory by default – decided in your SoA

What it means in plain language

Prepare for incidents in advance: define the process, roles, communication and tools before something happens.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Preparation fails when teams only know the headline response route but not the practical triggers, contacts, approvals, or handoffs. Teams should align the Incident Response Policy, Data Breach Notification Procedure, and Incident Register so the organization can act quickly without improvising during a stressful event. It also keeps the plan linked to business impact, legal deadlines, and evidence preservation needs.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • The plan names an incident team, but call trees, alternates, after-hours contact steps, and escalation authority are missing or stale, delaying first-hour action.
  • Severity definitions exist, yet they are not tied to example scenarios, legal notification checkpoints, customer communications, or tool ownership, causing inconsistent preparation.
  • Tabletop exercises are mentioned, but no agenda, action log, corrective follow-up, or updated register entry shows lessons were converted into prepared operating steps.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a small incident command structure with named primary and backup roles for triage, containment, legal review, communications, and evidence handling. Tie each role to a practical tool such as the ticketing queue, secure chat bridge, call tree, and the Incident Register so the first hour is routine, not improvised.
  • Build scenario-based preparation around phishing, ransomware, lost device, and supplier breach paths. For each scenario, list decision thresholds, who approves system isolation, when privacy or legal review is required, and what records must be opened, including incident IDs, timestamped notes, and communication drafts.
  • Maintain a communications map covering staff, customers, suppliers, regulators, and internal leadership. Record which template belongs to which audience, who can send it, where approval is logged, and which contact list is reviewed on a set cadence by the incident owner and a business continuity representative.
  • Run periodic tabletop exercises using realistic evidence packs, such as mock alerts, screen captures, and affected-asset lists. Capture gaps as corrective actions, assign owners and due dates, then update the policy, procedure, and register so the next activation reflects the tested lessons rather than a theoretical plan.

What an auditor will ask to see

  • Incident Response Policy with named roles, severity matrix, contact routes, and approval steps for communications.
  • Incident Register entries showing preparation exercises, scenario notes, owners, deadlines, and closure of follow-up actions.
  • Tabletop exercise pack with agenda, injects, participant list, decisions taken, and revised contact sheet or notification template.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.24. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.25 — Assessment and decision on information security events and A.5.26 — Response to information security incidents. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.