Incident response plan template (aligned with NIST CSF 2.0)
A free incident response plan template for software teams, aligned with NIST SP 800-61 Rev. 3 and CSF 2.0: roles, severity, steps, communication, and testing.
The alert says customer data may have been exposed. In the first ten minutes, four engineers are investigating in four directions, nobody has told legal, a support agent has already replied to a customer, and someone asks in the channel, "Who's in charge?" The technical response hasn't started yet.
An incident response plan answers those questions before the alert. This template is aligned with NIST's SP 800-61 Rev. 3, checked on 16 November 2026, and links to runbooks and postmortems for the detail.
The NIST framing
NIST published SP 800-61 Revision 3 in April 2025, replacing Revision 2 from 2012. It positions incident response within cybersecurity risk management as described by the NIST Cybersecurity Framework 2.0, whose core has six functions: Govern, Identify, Protect, Detect, Respond, and Recover. The aim, per NIST, is to prepare for incidents, reduce their number and impact, and make detection, response, and recovery more efficient.
In practice: preparation happens in Govern, Identify, and Protect; handling happens in Detect, Respond, and Recover.
The template
# Incident response plan
Owner: [Name] Last reviewed: [Date] Last tested: [Date]
## Scope
[What counts as an incident: security events, outages, data loss.]
## Roles
| Role | Responsibility | Who / rotation |
|---|---|---|
| Incident commander | Runs the response; makes the calls | [Rotation] |
| Technical lead | Leads investigation and fixes | [Rotation] |
| Communications lead | Internal and customer updates | [Name] |
| Scribe | Timeline and decisions log | [Rotation] |
| Legal / privacy | Notification obligations | [Name] |
## Severity
| Level | Definition | Response |
|---|---|---|
| SEV1 | Data breach, or full outage of a core service | Page now, all roles, exec update hourly |
| SEV2 | Major degradation or suspected breach | Page now, IC and tech lead |
| SEV3 | Minor impact, workaround exists | Next business day |
## Declaring an incident
- Anyone can declare one in [channel] with [command].
- Declare early; downgrading is cheap.
## Response steps
1. Assess: scope, severity, affected systems and customers.
2. Contain: stop the spread or the impact. Link runbooks.
3. Preserve evidence for security incidents before changing systems.
4. Eradicate and recover: remove the cause, restore service.
5. Verify: confirm recovery and monitor.
## Communication
| Audience | Owner | Channel | When |
|---|---|---|---|
| Responders | IC | Incident channel | Continuous |
| Leadership | Comms lead | [Channel] | SEV1 hourly |
| Customers | Comms lead | Status page, email | After IC approval |
| Regulators | Legal | As required | Per legal obligations |
## After the incident
- Postmortem within [5] business days for SEV1 and SEV2.
- Action items tracked with owners.
- Plan updated if it didn't work.
## Links
- Runbooks: [link]
- Contact list: [link]
- Postmortem template: [link]
How to use each section
Roles. The most important part. One incident commander, who coordinates and decides rather than debugging. Without one, everyone investigates and nobody leads.
Severity. Concrete definitions so nobody debates the level mid-incident. When in doubt, go higher.
Preserve evidence. For security incidents, restarting a server can destroy what you need to understand the breach. Make this explicit.
Communication. Who speaks to customers, and who approves it. Unapproved updates create a second incident.
Scribe. The timeline and decisions log becomes the postmortem's timeline.
Plan vs playbook vs runbook
| Document | Covers |
|---|---|
| Incident response plan | Roles, severity, process, and communication for any incident |
| Playbook | Response to one incident type, such as ransomware or credential leak |
| Runbook | Steps for one alert or procedure |
The plan stays short and stable; playbooks and runbooks carry the detail.
Testing with tabletop exercises
Walk the team through a scenario, such as "an API key for production was posted publicly," and ask at each step who acts, what they decide, and what they need. Gaps show up fast: an outdated contact, an unclear owner, a missing runbook. Update the plan after every exercise and every real incident.
Decisions during incidents
Incidents produce decisions under pressure: rotate all keys, disable a feature, roll back a release, delay a launch. The scribe captures them in the moment. Afterward, the ones that set lasting rules, such as "no production credentials in CI logs," need to reach everyone, including AI coding agents writing the next pipeline.
Where Lockstep fits
Lockstep captures decisions from documents, Slack, and pull requests, routes each to its owner for approval, and briefs Claude Code sessions on the ones that apply to the code being changed, so a rule set during an incident shapes the next change.
See how it works.
Sources checked 16 November 2026
- https://csrc.nist.gov/pubs/sp/800/61/r3/final
- https://en.wikipedia.org/wiki/NIST_Cybersecurity_Framework
Related reading
For learning afterward, see the blameless postmortem template. For on-call procedures, see the runbook template.
Frequently asked questions
- What is an incident response plan?
- A document that defines how an organization detects, responds to, and recovers from incidents: who is involved, how severity is judged, the steps to follow, how to communicate, and how to learn afterward. It applies to security incidents and, for many software teams, to outages too.
- What is NIST SP 800-61?
- NIST's guide to incident response. Revision 3, published in April 2025, replaced Revision 2 from 2012. It helps organizations build incident response into their cybersecurity risk management as described by the NIST Cybersecurity Framework (CSF) 2.0.
- What are the NIST CSF 2.0 functions?
- Six functions: Govern, Identify, Protect, Detect, Respond, and Recover. Incident response draws on all of them, from preparation under Govern, Identify, and Protect to handling incidents under Detect, Respond, and Recover.
- What is the difference between an incident response plan and a playbook?
- The plan is the overall framework: roles, severity, communication, and process for any incident. Playbooks and runbooks are step-by-step procedures for specific incident types or alerts, such as ransomware or a database outage, and the plan links to them.
- How do I test an incident response plan?
- Run tabletop exercises: walk the team through a realistic scenario and check who would do what, which decisions would be needed, and where the plan is unclear. Update the plan after each exercise and each real incident.
Keep reading