Guide Incident Response Cybersecurity

Building an Incident Response Plan: A Practical Guide

Most organisations know they should have an incident response plan. Few have one that has been tested, is stored somewhere accessible during an incident, and covers who makes decisions under pressure.

17 August 2026
Updated 10 November 2026
10 min read
Key takeaways
  • An incident response plan is primarily a people and process document. It defines who makes decisions, in what order, with what authority. Technical steps fail without that structure.
  • NIST SP 800-61 Revision 3 (April 2025) now places incident response inside the NIST Cybersecurity Framework 2.0. For day-to-day procedures, most teams still work through six operational steps, from Preparation to Post-Incident Activity. Skipping the post-incident review means the same mistakes repeat.
  • Store the plan somewhere accessible when your systems are down or encrypted. Print a copy. A plan that lives only on the network is unavailable during the incidents it is designed for.
  • Notification deadlines depend on where you operate and whose data is affected: 72 hours to the regulator under UK and EU GDPR, three working days in Brazil, and four business days for a material incident at a US-listed company. One incident can start several clocks at once, so the plan should list every regime that applies to you.
  • Tabletop exercises consistently surface the same gaps: unclear escalation paths, an incomplete external contact list, and a communication approval chain too slow for a real incident.
  • Every named role needs a backup. The plan that has one owner who is unreachable when the incident occurs is the plan that will not be followed.

What an incident response plan is

Most organisations treat incident response as something to work out when something goes wrong. The result is predictable: decisions made under pressure, by people who have never faced this situation, without a clear escalation path, defined communication protocol, or recovery sequence. Containment takes longer. Evidence is lost. Notifications are late. Costs multiply.

An incident response plan documents the process your organisation follows from the moment a security incident is detected through to restoration, legal compliance, and post-incident review. It defines who does what, in what order, with what authority, and who is told what and when.

The plan is a people and process document. Before an incident, it should settle who can take a production system offline, who approves external statements, who contacts the regulator, who briefs the board and who decides whether to pay a ransom. The technical steps follow from those answers. When a real incident response goes wrong, the cause is more often process and communication than a technical gap.

Incident response documentation usually comes in three layers. An incident response policy is short and sets the rules: who holds authority, what staff must report and what the organisation requires. The plan, which this guide covers, explains how you activate a response, coordinate it, escalate, communicate and recover. Playbooks hold the actions for one type of incident, such as ransomware or a supplier outage. Keep detailed technical procedures in the playbooks, or the plan grows too long to use in a crisis.

247
days: average time to identify and contain a breach globally, up for the first time in five years (IBM 2026)
$4.99M
global average cost of a data breach, up 12% year on year to a record high (IBM 2026)
72h
deadline, where feasible, for notifying the regulator of a reportable personal data breach under UK and EU GDPR

Eight steps to build the plan

Each step below produces something you can point to. If a step has no output yet, that part of the plan does not exist.

1
Set the scope and name an owner
Decide which parts of the organisation, which countries and which incident types the plan covers, and who owns it. Output: a one-page scope statement with a named plan owner and an executive sponsor.
2
List critical services, data and suppliers
Work out which services the business cannot run without, the systems and data behind them and the suppliers they depend on. Output: a ranked list of critical services with recovery time and recovery point objectives, and a first version of the critical supplier register.
3
Map your notification duties
Check every law, regulator and contract that could require you to report an incident. Output: a notification matrix listing each regime, its threshold, its deadline, the regulator, how to file and who decides. Include the notification deadlines in your customer contracts.
4
Define severity levels and escalation
Agree what makes an incident P1, P2 or P3 and who is told at each level. Output: a severity matrix like the example in our plan contents guide and an escalation tree with names and deputies.
5
Assign roles and decision rights
Name the incident lead, technical lead, communications lead, legal and data protection contacts and the executive who signs off major decisions, each with a deputy. Output: a role list stating who can take systems offline, approve external statements, notify a regulator and decide on a ransom.
6
Build the contact list and fallback channel
Collect internal, supplier, insurer, legal, regulator and law enforcement contacts, and agree how the team talks if email and single sign-on are down. Output: a contact sheet held offline and a tested out-of-band channel.
7
Write playbooks for your likeliest incidents
Start with three to five scenarios, such as ransomware, email compromise, a personal data breach and a supplier incident. Output: one playbook per scenario, each short enough to follow under pressure.
8
Assemble, store and test
Put the pieces into one document in the order shown below, have the executive sponsor approve it, store copies where an attacker cannot reach them, and book the first exercise. Output: version 1.0 of the plan, signed off, an offline copy and a date for the first tabletop exercise.

Three companion guides cover the parts that take the most work: what the plan must contain, including the six phases and an example severity matrix for step 4; the first-hour checklist and playbooks for step 7; and notification duties for step 3.

Assembled, the plan document usually runs in this order:

  1. Purpose, scope and the plan owner
  2. Roles, deputies and decision rights
  3. Severity levels and escalation
  4. The first-hour checklist
  5. Communication and notification procedures, including the notification matrix
  6. Playbooks, or a list of them with where each is kept
  7. Recovery priorities and the handoff to disaster recovery and business continuity
  8. Closure criteria and the post-incident review
  9. Appendices: the contact sheet, the critical supplier register, message templates and a blank decision log

Regulatory and contractual notification

One incident can start several reporting clocks at once: 72 hours to the regulator under UK and EU GDPR, three working days in Brazil and four business days for a material incident at a US-listed company, plus sector rules and the deadlines in your customer contracts. Containing the incident stops none of them, which is why step 3 builds the notification matrix before anything happens.

Our guide to incident notification duties covers the questions to work through for each regime and the UK rules in detail, with a summary for other countries. To look up a deadline country by country, see breach notification deadlines by country.

Store the plan where it will be accessible

This point is mentioned consistently in post-incident reviews and consistently ignored in advance: if your incident response plan lives on SharePoint, in your email system, or on a network drive, it may be unavailable precisely when you need it.

A ransomware attack that encrypts file servers and cloud-synced drives also encrypts the incident response plan stored there. A plan that cannot be accessed during an incident is not a plan. Store a current copy offline, in print, and in a location known to all response team members. Include the external contact list in the printed version. Consider storing it with your cyber insurance documentation.

Testing the plan

An untested plan is a set of assumptions. Three levels of testing exist, each appropriate for different stages of programme maturity.

📋
Tabletop exercise
A facilitated walkthrough of a specific scenario. No systems are touched; participants talk through their decisions in sequence. A skilled facilitator introduces complications: the CISO is unavailable, the backup server is also affected, a journalist has called. Tabletop exercises surface ambiguity, gaps in decision authority, and bottlenecks in the communication approval chain without operational disruption. Achievable in half a day. Run at minimum annually, and after any significant change to personnel, systems, or the business.
🔧
Functional exercise
Selected teams execute specific plan components for real: the IT team isolates a test system, the communications team drafts a customer notification, legal counsel reviews regulatory obligations against a sample scenario. Tests individual plan components without full organisational mobilisation. Appropriate once a tabletop has established that the plan structure is sound.
🚨
Full simulation
End-to-end exercise of the full plan under realistic conditions. Resource-intensive and requires careful scoping to avoid operational disruption. Appropriate for organisations with mature programmes or high-impact obligations such as critical infrastructure operators and regulated financial firms. Full simulations that include backup restore testing and communications chain activation provide the most realistic assessment of actual response capability.

Tabletop exercises tend to expose the same gaps: the escalation path is unclear when the primary contact is unavailable, the external contact list is incomplete or has outdated numbers, the communication approval chain has too many steps for a fast-moving incident, and team members do not know where the plan is stored.

Run at least one exercise where the incident starts at a supplier: your MSP reports a breach late on a Friday, or your main cloud platform is unavailable for two days. Most plans have never been tested against this. It shows who has the authority to cut a supplier's access, how long the manual workaround really lasts, and what you tell customers before the supplier has given you answers.

Measure each exercise against the plan's own targets: how long it took to declare the incident, to reach the decision-makers, to decide on notification and to get the out-of-band channel working. Record every gap as a corrective action with an owner and a due date, and check those actions at the start of the next exercise.

Common mistakes

Single point of failure in ownership. A plan with one named owner who is unreachable during an incident defaults to improvisation. Every role needs a backup. The backup needs to know they are the backup.

The plan stops at containment. Many organisations document detection through containment and treat recovery as obvious. The recovery sequence, the monitoring requirements during recovery, and the conditions for returning systems to production all need to be explicit. Recovery without monitoring is an invitation for re-infection.

No communication template. Drafting customer, supplier, or media communications during an active incident, under legal scrutiny and time pressure, produces inconsistent and legally problematic output. Pre-drafted templates reviewed by legal counsel reduce both the time and risk involved.

The plan was never tested. A plan written once and filed away reflects the environment as it was when it was written. People, systems, suppliers, and regulatory obligations change. Test it, or you cannot know how your team will perform. Update it, or it describes an organisation that no longer exists. Name an owner for the plan, review it at least annually, and update it after major system or supplier changes, acquisitions, changes in regulatory scope, and every exercise or real incident.

Backup access is not verified. The most important part of ransomware recovery is a backup that can be restored under time pressure to a usable state. Many organisations have backups they have never restored. Until you have restored from a backup under realistic conditions, you do not know whether it will work.

Assuming the supplier will tell you. Many supplier contracts say little about breach notification, and a supplier in the middle of its own incident is slow to share detail. Check the notification clause for each critical supplier, agree a named contact on both sides, and plan to act on partial information. If you wait for the supplier's full report, your own 72 hours may run out first.

Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Common questions

Does every organisation need an incident response plan?

Any organisation that holds personal data, operates critical services, or relies on IT to function needs one. Under UK and EU GDPR, organisations must report qualifying personal data breaches to the regulator within 72 hours where feasible, and Brazil's LGPD allows three working days. Those deadlines are not achievable without a documented response process. Organisations in scope of the UK NIS Regulations must report significant incidents within 72 hours, and those operating in the EU may also face NIS2's 24-hour early warning. For smaller organisations outside those direct obligations, the business case remains clear: an incident handled without a plan costs more and takes longer to contain. A minimum viable plan covering roles, escalation paths, and two or three playbooks takes days to produce. The cost of not having it shows up in every breach that could have been contained faster.

How long does it take to build an incident response plan?

A minimum viable plan covering roles, escalation paths, a contact list, and two or three specific playbooks typically takes three to five working days with the right stakeholders engaged. A fuller plan covering five or more incident types, notification procedures for each data protection law and sector rule that applies, pre-drafted communication templates, and a completed tabletop exercise typically takes two to four weeks, depending on the size of the organisation, how much documentation already exists and how many scenarios you cover. Write the minimum viable plan first and extend it later; do not hold it back until the full version is ready. Start with what would happen if ransomware hit on a Monday morning, and build from there.

Cybersecurity Assessment

Know your risks before an incident forces the conversation

Our assessment covers your incident response readiness alongside four other security domains. You leave with a prioritised roadmap.

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, or professional advice. Cyvra makes no warranty as to the accuracy or completeness of this content, which may not reflect the most current regulatory developments. Readers should seek independent legal and regulatory advice appropriate to their specific circumstances. Cyvra accepts no liability for any loss arising from reliance on this content.