Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An incident response plan sets out who decides what, who is called, and what happens in the first hours of a security incident, so that the response does not have to be invented under pressure.

What Is an Incident Response Plan?
An incident response plan is the document that converts good intentions into decisions somebody can make at two in the morning. It names roles, sets thresholds, lists contacts, and records what authority each person has. Its value is almost entirely in the decisions taken in advance — during an incident, nobody reads a forty-page document, they follow a one-page checklist written by someone who had time to think.
If an intruder is in the corporate email system, the response cannot be coordinated in the corporate email system. Agree a separate channel in advance — a messaging platform on a different tenant, a conference bridge, or a phone tree — and make sure the plan itself is available when the file server is encrypted. Printed copies in the incident folder are not an anachronism; they are the reason some organisations started responding on day one rather than day three.
The plan sets the framework. Playbooks handle the scenarios you are actually likely to face: ransomware, business email compromise, a compromised privileged account, data exfiltration, a critical vulnerability in an internet-facing application, and failure of a key supplier. Each should fit on one or two pages, list the first ten actions in order, and name the decisions that need sign-off. Write them for the scenarios in your own risk register rather than copying a generic set.
UK GDPR gives 72 hours from awareness to notify the ICO where a personal data breach is likely to result in a risk to individuals. The NIS Regulations 2018 set their own deadline for operators of essential services. Regulated financial firms have obligations to the FCA, and entities in scope of DORA face a four-hour initial notification after classification. Put the thresholds, the forms, and the person responsible for filing directly in the plan, because the first hours of an incident are when nobody wants to be reading legislation — see breach notification for the detail.
Exercise it at least annually, including at board level, and include the awkward variants: the incident lead is unreachable, the backup restore takes four days rather than four hours, the attacker contacts a journalist before you contact your clients. The NCSC’s Exercise in a Box offers free scenarios for organisations starting out, and a facilitated tabletop produces a more honest action list than a self-run one.
Review the plan after every real incident as part of the lessons learned review, and whenever the business changes shape. At Privia Security, we help organisations write and rehearse these plans through our emergency action plan services, and the exercise almost always finds the gap before an attacker does.
Short enough to be used. Twenty to thirty pages covering roles, authority, severity, contacts, communications, and evidence handling is typical, with one-page playbooks for specific scenarios and a single-page checklist for the first hour. Length is a poor proxy for quality, and plans that read like policy documents tend to sit unopened during real incidents.
At least annually, and after any significant change to the business, the technology estate, or the regulatory position. A tabletop exercise covering a realistic scenario is the minimum. Larger organisations supplement it with technical simulations and unannounced call-out tests, which reveal practical failures such as out-of-date contact details far more reliably than a planned exercise.
Both. Name the role so the plan survives staff turnover, and list the current holder with a deputy in an annexe that is easy to update. Contact details go in the annexe, not the body, and should be reviewed quarterly. Every named role needs a deputy, because incidents do not wait for people to return from leave.
Yes. The retainer supplies capability, not decisions. Your plan still has to say who authorises containment, who notifies the regulator, how staff and clients are told, and what the provider is given access to on arrival. Providers work fastest where that groundwork exists, and slowest where the first day is spent obtaining credentials and diagrams.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.