ISO 27001 Control A.5.24: Information Security Incident Management Planning and Preparation

· 8 min read · Lyudmil Arkov

Nobody decides how to handle a security incident well while it is happening. The people who cope best are the ones who already know who is in charge, who to call, what to write down and what not to touch. A.5.24 is the control that makes that possible. It is the 24th of 37 organizational controls in our walk through Annex A, and the first of five that together cover the life of an incident.

Think of it as the fire drill rather than the fire. The following controls cover assessing, responding and learning. This one is about being ready: having a process, having named people, and having told everyone how it works before the pressure arrives.

What the control requires

Annex A control 5.24 of ISO 27001:2022 states that the organization shall plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities.

The key elements:

  • Plan and prepare - the work happens before an incident, not during one
  • Processes - a defined way to report, assess, respond to and close incidents
  • Roles and responsibilities - named people or functions, with deputies, who know what they own
  • Defining, establishing and communicating - writing it down is not enough; it must be put in place and people must hear about it

A.5.24 is a corrective control in the attributes of ISO/IEC 27002:2022, because it prepares the organization to deal with incidents and limit their damage. Annex A states the control; ISO 27002 gives guidance, including the idea of a central point of contact for reporting, a competent response capability and relationships with outside parties. The planning does not need to be heavy. A ten-person company needs a clear one-page process more than a forty-page manual.

How to implement incident management planning

Write a process that people can actually use

Cover the basic stages: how an event is reported, how it is assessed, how a response is run, how it is closed and how lessons are captured. Each stage should say who does what. Keep the language plain and the steps short, because the person reading it may be stressed and half awake. Include:

  • A single place to report, such as a shared mailbox, chat channel or phone number that is monitored
  • A simple way to record each incident: date, reporter, what was observed, who took ownership
  • Contact details for the response team, kept somewhere accessible when your main systems are down
  • A definition of what counts as an event, an incident and a major incident, so people know when to escalate

Print the key page or keep an offline copy. An incident plan stored only on the server that has just been encrypted by ransomware is a classic oversight.

Assign roles with deputies

Name an incident lead, someone who communicates with management and customers, someone with technical authority to isolate systems, and someone who keeps the log. In a small business one person may hold several roles, but write that down and name a backup for holidays and illness. Connect this to your wider information security roles and responsibilities so that incident duties appear in job descriptions and not only in an appendix.

Decide who has the authority to take hard decisions quickly, such as taking a service offline or notifying a customer. If every such choice needs a committee, response will be slow exactly when speed matters.

Prepare the outside relationships

Some incidents need more than your own team. Identify in advance who you would call: a forensic or incident response specialist, your cloud and hosting providers, your insurer, legal counsel, and where relevant the authorities. Contact with authorities covers the regulator and law enforcement side, and contact with special interest groups helps you stay informed about threats. Notification duties under data protection or sector rules vary by jurisdiction, so we suggest confirming deadlines with qualified advisers and recording them in the plan rather than relying on memory.

Your suppliers matter too. Agree how a provider will tell you about an incident on their side, and how you reach them out of hours, as discussed in information security for use of cloud services.

Communicate it and rehearse it

A plan that people have never heard of will not be used. Cover it in induction and in information security awareness, education and training, and make sure everyone knows the one thing that matters most: how to report. Then rehearse. A tabletop exercise of an hour, where you walk through a scenario such as a lost laptop, a phishing compromise or a supplier breach, will show the gaps faster than any review. Write down what you found and fix it. Run a different scenario next time, and include someone from management so that decisions about communication and customers are tested too.

Decide how you will rank incidents so that the response is proportionate. Three or four levels are usually enough, defined by impact rather than by technical detail: for example, whether customer data is involved, whether a critical service is down, and whether the problem is still spreading. For each level, say who is informed, how fast, and whether management must be woken up. Having this agreed in calm conditions avoids long debates in the middle of a crisis.

Preparation also means resources. Check that the response team has the access it needs, such as administrator rights, backups, log sources and a way to communicate if email is unavailable. Keep a small list of tools and accounts the team can use, and confirm that your logging captures enough to reconstruct what happened. Budget matters as well: if you would need an outside specialist, it helps to have the contract or a retainer discussion done before the day you need them. Finally, set a review rhythm. Look at the plan at least once a year and after any real incident, update contact details, and record the date of the last review so the version history shows the process is maintained.

A.6.8 connection. Information security event reporting is the intake side of the process: how staff raise what they see.

A.5.2 connection. Information security roles and responsibilities is where the incident roles belong.

A.5.5 and A.5.6 connection. Contact with authorities and contact with special interest groups provide the outside relationships the plan relies on.

A.5.7 connection. Threat intelligence helps you choose realistic scenarios to plan and rehearse for.

Clause 7.4 connection. Communication requires you to decide what to communicate, when and to whom; incident communication is a sharp example.

Clause 10.2 connection. Nonconformity and corrective action is the management system’s route for fixing the root causes that incidents expose.

Forward reference. The next four controls follow the incident through its life: assessment and decision on information security events (A.5.25), response to information security incidents (A.5.26), learning from information security incidents (A.5.27) and collection of evidence (A.5.28). We cover each of them in the coming days.

What auditors check

A documented process. Auditors expect an incident management procedure covering reporting, assessment, response and closure.

Defined roles. They look for named roles, deputies and evidence that the people involved know their part.

Communication. They interview staff to see whether people know how to report, which often reveals more than the document does.

Contact lists. They check that contact details for the response team, suppliers and authorities exist and are current.

Exercises and tests. Records of tabletop exercises or real incidents, with the actions that followed, show the plan is alive.

Alignment with other processes. They look for links to business continuity, supplier management and the ISMS corrective action process.

Common mistakes to avoid

A plan that nobody has read. If people cannot say how to report an incident, the plan does not exist in practice.

No out-of-hours route. Incidents do not wait for office hours. Decide who is reachable and how.

Everything depends on one person. Holidays happen. Name deputies and check that they have the access they need.

Unclear definitions. Staff who do not know what counts as an incident will either report everything or nothing. Give simple examples.

Never testing. An untested plan almost always has a broken phone number or a missing permission somewhere.

Planning only for cyber attacks. Lost devices, misdirected emails and physical theft are far more frequent than dramatic intrusions, and the plan should handle them.

How 27kay can help

We help organizations build incident management that fits their size, from a one-page process for a small team to a structured capability for a larger one. As part of ISO 27001 implementation, we help you define roles, run a first tabletop exercise and prepare the records an auditor will ask for. For the full picture, see our ISO 27001 knowledge hub.

If your main systems went down tonight, would everyone know who leads, who to call and where the plan is kept? Get in touch - we will help you make sure the answer is yes before you need it.