# Incident response plan: what it contains and how to build one

Guide, read 16 November 2026

**The short answer.** An incident response plan is the written roadmap that says who decides what, who is called and which steps follow once a cybersecurity incident is declared. This page, read on 16 November 2026, lists the sections a plan needs, the laws that require one, and links to a free template, steps and playbooks.

## What is an incident response plan?

An incident response plan is the written roadmap for handling cybersecurity incidents. NIST SP 800-61 Rev. 3 (April 2025) says incident response plans provide the roadmap for implementing the incident response capability, and sit beside vulnerability management plans and business continuity plans (CSF outcome ID.IM-04).

A good plan names roles, defines when an incident is declared, sets who may take which action, lists who must be told and when, and says how the plan is tested and kept current.

## What goes in an incident response plan?

A plan needs fifteen parts in this template set, from purpose and roles to forms. The table lists each part with the NIST CSF 2.0 outcomes it answers; the full mapping, with ISO/IEC 27001 control numbers, is on the standards map.

The FTC Safeguards Rule shows what a regulator expects at a minimum. It requires a written plan that addresses seven areas: goals, internal processes, roles and decision-making authority, communications and information sharing, remediation of weaknesses, documentation and reporting, and revision after a security event.

| Plan section | What it answers | CSF 2.0 outcomes |
| --- | --- | --- |
| 1. Purpose, scope and authority | Who owns the plan, what it covers and who may act | GV.PO-01, GV.PO-02, ID.IM-04, GV.RR-02 |
| 2. Roles and responsibilities | Who does what, with deputies | GV.RR-01, GV.RR-02, PR.AT-02 |
| 3. Contact and escalation sheet | Who to call, day or night | RS.CO-02, RS.CO-03, GV.SC-08 |
| 4. Severity levels | How serious an incident is and who is called | RS.MA-03, DE.AE-04, RS.AN-08 |
| 5. Detecting, reporting and declaring an incident | How an incident is reported and declared | DE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-02 |
| 6. Triage and analysis | How the incident is validated, scoped and categorized | RS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-04 |
| 7. Containment | What may be isolated or blocked, and who approves | RS.MI-01, RS.MA-04 |
| 8. Eradication and recovery | How the threat is removed and service restored | RS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-06 |
| 9. Communications | Who says what to whom | RS.CO-02, RS.CO-03, RC.CO-03, RC.CO-04 |
| 10. Legal, regulatory, contractual and insurance notices | Which laws, contracts and policies set notice clocks | GV.OC-03, RS.CO-02 |
| 11. Evidence handling and documentation | How facts and evidence are recorded | RS.AN-06, RS.AN-07 |
| 12. Third parties and suppliers | What suppliers must tell you and when | GV.SC-08, DE.CM-06, RS.MA-01 |
| 13. Post-incident review | How lessons are captured and acted on | ID.IM-03, ID.IM-04, RC.RP-06 |
| 14. Testing, training and keeping the plan current | How the plan is tested and kept current | ID.IM-02, ID.IM-04, PR.AT-02, GV.PO-02 |
| Appendices: forms | Forms to use during an incident | RS.AN-06, RC.RP-06 |

What goes in an incident response plan?

## Which laws require a written incident response plan?

Two rules read for this site name a written plan. The FTC Safeguards Rule, 16 CFR 314.4(h), requires financial institutions under FTC jurisdiction to establish a written incident response plan. New York's 23 NYCRR 500.16 requires covered entities to establish incident response plans and test them at least annually.

Other rules set notice duties rather than a plan, such as the HIPAA Breach Notification Rule and GDPR Article 33. The [company-type templates](/templates/) show each rule with its source.

## How do you build a plan from this site?

Start with the [free template on the home page](/), which is in full on the page and as a Word and PDF download. Fill the bracketed fields, then walk the plan through with the people named in it.

The [guide to creating a plan](/plans/how-to-create-an-incident-response-plan/) gives the order of working sessions. The [steps](/steps/) and [playbooks](/playbooks/) pages cover what happens during an incident.

## All plan guides

- [What is an incident response plan?](/plans/what-is-an-incident-response-plan/)
- [How to create an incident response plan](/plans/how-to-create-an-incident-response-plan/)
- [How to test an incident response plan](/plans/how-to-test-an-incident-response-plan/)
- [Incident response plan vs playbook](/plans/incident-response-plan-vs-playbook/)
- [Incident response plan vs business continuity plan](/plans/incident-response-plan-vs-business-continuity-plan/)
- [Incident response policy: what it is and who approves it](/plans/incident-response-policy/)
- [Incident response roles and responsibilities](/plans/incident-response-roles-and-responsibilities/)
- [Incident response severity levels](/plans/incident-response-severity-levels/)

## Related pages

- [Free incident response plan template](/)
- [Glossary](/glossary/)
- [FAQ](/faq/)
- [Incident response steps: the order and who does what](/steps/)
- [Incident response playbook: what it is and how to build a library](/playbooks/)
- [The standards map](/standards-map/)

## Sources

- NIST SP 800-61 Rev. 3, full text (April 2025): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026)
- eCFR, 16 CFR Part 314, Standards for Safeguarding Customer Information: https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-314 (read 16 November 2026)
- 23 NYCRR 500.16, Incident Response Plan (Cornell LII): https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.16 (read 16 November 2026)
- NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references: https://csrc.nist.gov/extensions/nudp/services/json/csf/download?olirids=all (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/
