- 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.
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.
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:
- Purpose, scope and the plan owner
- Roles, deputies and decision rights
- Severity levels and escalation
- The first-hour checklist
- Communication and notification procedures, including the notification matrix
- Playbooks, or a list of them with where each is kept
- Recovery priorities and the handoff to disaster recovery and business continuity
- Closure criteria and the post-incident review
- 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 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 has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile