# 17 questions about incident response plans, answered

FAQ, read 16 November 2026

**In short.** 17 short answers on what an incident response plan is, how to create and test one, the steps, playbooks and the data breach plan. Each answer is drawn from NIST, CISA, SANS, the NCSC or the rule text, with the read date on the pages it links to.

## What are the most common questions about incident response plans?

The questions below come from what people search for: what a plan is, how it differs from a playbook, policy or continuity plan, how to create and test it, and what a breach plan includes.

**What is an incident response plan?**

An incident response plan is a written roadmap for handling cybersecurity incidents: who decides, who is called, what happens in each phase and how the plan is tested. NIST SP 800-61 Rev. 3 says incident response plans provide the roadmap for implementing the incident response capability (read 16 November 2026).

**What is the difference between an incident response plan and a playbook?**

The plan sets roles, authorities, severity and notice rules for every incident. A playbook gives the actionable steps for one scenario. NIST SP 800-61 Rev. 3 says playbooks provide actionable steps for various scenarios and points to CISA's federal playbooks as examples.

**What is the difference between an incident response plan and a business continuity plan?**

The incident response plan handles the security event; the business continuity plan keeps operations running through disruption. NIST advises synchronizing them because incidents can undermine business resilience, and the NCSC says to link the two with disaster recovery and crisis management plans.

**What is the difference between an incident response plan and an incident response policy?**

The policy is the short, approved statement of management commitment, scope, definitions and authorities. The plan is the operating roadmap beneath it. NIST SP 800-61 Rev. 3, section 2.3, lists the usual policy elements and says processes and procedures are based on the policy and plan.

**How do you create an incident response plan?**

Work through five sessions: scope and roles; severity and declaration rules; contacts and legal notices; actions by phase; then a walkthrough. The NCSC advises involving IT security, legal, human resources, public relations and suppliers, with senior management backing critical decisions.

**How do you test an incident response plan?**

Walk every named role through a realistic scenario at least once a year and time each decision. Also test restoring from backups. The NCSC offers a free Exercise in a Box, and New York 23 NYCRR 500.16(d) requires annual testing of plans and backup restores for covered entities.

**How do you add forensics to an incident response plan?**

Add an evidence section: preserve logs and, where the technical lead decides, capture memory and disk images before changing a system; record who collected what and when. NIST outcomes RS.AN-06 and RS.AN-07 cover recording actions and preserving the integrity of incident data. CISA lists memory and disk imaging.

**Who approves the incident response policy?**

NIST does not name one approver. Its outcome GV.RR-01 makes organizational leadership responsible and accountable for cybersecurity risk, so the most senior leader accountable signs. Write the title and approval date into the plan. Under the FTC Safeguards Rule the Qualified Individual reports to the board at least annually.

**What are the steps in incident response?**

CISA's playbook uses five: preparation, detection and analysis, containment, eradication and recovery, and post-incident activities. The SANS handbook uses six: preparation, identification, containment, eradication, recovery and lessons learned. NIST SP 800-61 Rev. 3 maps response to six CSF 2.0 Functions.

**What is the correct order of incident response steps?**

Prepare, detect and analyze, contain, eradicate and recover, then learn. The steps overlap: CISA says eradication and recovery can run at the same time, and new signs of compromise send responders back to analysis. NIST says lessons should be shared as soon as they are identified.

**How do the NIST and SANS incident response steps compare?**

They cover the same work. The previous NIST model has four phases, SANS has six because it splits containment, eradication and recovery, and NIST Rev. 3 (April 2025) uses the CSF 2.0 Functions with improvement running throughout.

**What does an incident response plan for a small business need?**

A named lead, outside help on call, tested backups, a list of what counts as an incident, a first-hour routine and a list of who to tell. The NCSC guide organizes this as five steps: prepare, identify, resolve, report and learn.

**Is there an incident response plan template based on NIST?**

NIST has not published a fill-in template. SP 800-61 Rev. 3 (April 2025) is a CSF 2.0 Community Profile with recommendations. The NIST layout template on this site groups a plan under the CSF Functions and shows the outcome codes each section answers.

**Is there an incident response plan template from CISA?**

CISA publishes playbooks rather than a fill-in plan. Its Cybersecurity Incident & Vulnerability Response Playbooks (November 2021) include an incident response checklist and a preparation checklist as appendices. They are written for federal civilian agencies and follow NIST SP 800-61 Rev. 2.

**What is an incident response playbook?**

A playbook is a set of actionable steps for one scenario. NIST SP 800-61 Rev. 3 says playbooks provide actionable steps or tasks for people to perform in various situations. Microsoft's public playbooks each include prerequisites, a workflow, a checklist and investigation steps.

**What should a data breach response plan include?**

A written policy and team, a map of where personal data lives, monitoring, training, then validate, scope, notify data owners, decide on law enforcement and decide on notifying individuals. Notices must meet the law: GDPR Article 33(3) and 45 CFR 164.404(c) list the content.

**How does GDPR affect a data breach response plan?**

GDPR Article 33 requires a controller to notify the authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk. Article 33(5) requires documenting every breach and Article 34 covers telling individuals at high risk.

## Related pages

- [Free incident response plan template](/)
- [Incident response plan guide](/plans/)
- [Incident response steps](/steps/)
- [Playbook library](/playbooks/)
- [Glossary](/glossary/)
- [Data breach response plan](/data-breach/)

## 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)
- NCSC, 10 Steps to Cyber Security: Incident management (11 May 2021): https://www.ncsc.gov.uk/collection/10-steps/incident-management (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)
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021): https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.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)
- SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026)
- NCSC, Small Business Guide: Response & Recovery: https://www.ncsc.gov.uk/collection/small-business-guidance--response-and-recovery (read 16 November 2026)
- NIST SP 800-61 Rev. 3, publication page (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 16 November 2026)
- Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026)
- U.S. Department of Education PTAC, Data Breach Response Checklist (September 2012): https://studentprivacy.ed.gov/sites/default/files/resource_document/file/checklist_data_breach_response_092012_0.pdf (read 16 November 2026)
- Regulation (EU) 2016/679 (GDPR), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679 (read 16 November 2026)
- eCFR, 45 CFR 164.404, Notification to individuals: https://www.ecfr.gov/current/title-45/section-164.404 (read 16 November 2026)

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