GuideChecked 16 November 2026
How to create an incident response plan
How do you create an incident response plan?
Work in five sessions of about two hours each, and finish each with a named owner for the next one. Session one agrees scope and the people for each role. Session two sets severity levels and the criteria for declaring an incident. Session three builds the contact sheet and the legal notice list.
Session four writes what happens in each phase, from triage to recovery. Session five is a walkthrough of a realistic scenario, which finds the gaps before an attacker does. The free template supplies the structure.
- Scope, owner and roles (sections 1 and 2).
- Severity and declaration (sections 4 and 5).
- Contacts and notices (sections 3 and 10).
- Actions by phase (sections 6 to 9 and 11 to 13).
- Walkthrough and sign-off (section 14).
Who should be in the room?
The NCSC says to involve the IT security team and also legal, human resources and public relations staff, plus suppliers and vendors, with senior management supporting critical decisions such as media handling. It also says to appoint specific individuals, or an incident response supplier, and give them clear terms of reference to make decisions.
NIST SP 800-61 Rev. 3, section 2.2, lists the same families of roles: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security and asset owners.
How do you write incident response plan text people can act on?
Write each rule with a trigger, an owner and a decision. Say "the incident lead declares an incident when an event shows unauthorized access to a system that holds customer data" instead of "serious events are escalated". Name roles and deputies, and give times in minutes or hours.
NIST says a policy should state which roles have authority to confiscate, disconnect or shut down technology assets. Put those authorities in the plan so that no one waits for permission during a containment decision.
- Use one verb per step: isolate, reset, call, record.
- Put the owner first: "Technical lead: isolate the device."
- Give a time or a trigger: "within 15 minutes of declaration".
- Keep reasons out of the steps; put them in a short note below.
What mistakes make a plan fail?
The common failures are a plan no one has read, contacts that are out of date, no one with authority to act, and no check against the legal clocks. The NCSC advises establishing escalation criteria and identifying specific situations where the technical team can act autonomously.
A plan that is never exercised is a draft. See how to test an incident response plan.
Related pages
- Incident response plan: what it contains and how to build one
- Free incident response plan template
- Incident response severity levels
- What is an incident response plan?
- How to test an incident response plan
- Incident response plan vs playbook
- Incident response steps: the order and who does what
- Incident response playbook: what it is and how to build a library
Sources
- NCSC, 10 Steps to Cyber Security: Incident management (11 May 2021)
- NIST SP 800-61 Rev. 3, full text (April 2025)
Last reviewed 16 November 2026. Each source above was read that day.