Skip to content
Incident Response Plan Templates

GuideChecked 16 November 2026

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

Open the free templateRead the method

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.

What goes in an incident response plan?
Plan sectionWhat it answersCSF 2.0 outcomes
1. Purpose, scope and authorityWho owns the plan, what it covers and who may actGV.PO-01, GV.PO-02, ID.IM-04, GV.RR-02
2. Roles and responsibilitiesWho does what, with deputiesGV.RR-01, GV.RR-02, PR.AT-02
3. Contact and escalation sheetWho to call, day or nightRS.CO-02, RS.CO-03, GV.SC-08
4. Severity levelsHow serious an incident is and who is calledRS.MA-03, DE.AE-04, RS.AN-08
5. Detecting, reporting and declaring an incidentHow an incident is reported and declaredDE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-02
6. Triage and analysisHow the incident is validated, scoped and categorizedRS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-04
7. ContainmentWhat may be isolated or blocked, and who approvesRS.MI-01, RS.MA-04
8. Eradication and recoveryHow the threat is removed and service restoredRS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-06
9. CommunicationsWho says what to whomRS.CO-02, RS.CO-03, RC.CO-03, RC.CO-04
10. Legal, regulatory, contractual and insurance noticesWhich laws, contracts and policies set notice clocksGV.OC-03, RS.CO-02
11. Evidence handling and documentationHow facts and evidence are recordedRS.AN-06, RS.AN-07
12. Third parties and suppliersWhat suppliers must tell you and whenGV.SC-08, DE.CM-06, RS.MA-01
13. Post-incident reviewHow lessons are captured and acted onID.IM-03, ID.IM-04, RC.RP-06
14. Testing, training and keeping the plan currentHow the plan is tested and kept currentID.IM-02, ID.IM-04, PR.AT-02, GV.PO-02
Appendices: formsForms to use during an incidentRS.AN-06, RC.RP-06

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 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 gives the order of working sessions. The steps and playbooks pages cover what happens during an incident.

All plan guides

Sources

  1. NIST SP 800-61 Rev. 3, full text (April 2025)
  2. eCFR, 16 CFR Part 314, Standards for Safeguarding Customer Information
  3. 23 NYCRR 500.16, Incident Response Plan (Cornell LII)
  4. NIST CSF 2.0 Reference Tool download, with ISO/IEC 27001:2022 informative references

Last reviewed 16 November 2026. Each source above was read that day.