# Incident Response Plan Templates: every page as markdown Free incident response plan templates in full on the page and as Word and PDF: a general plan, plans by company type, playbooks by incident type, the steps and a data breach plan, each with its source and read date. --- # 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/ --- # What is an incident response plan? Guide, read 16 November 2026 **The short answer.** An incident response plan is a written document that tells an organization how to detect, declare, contain, recover from and learn from a cybersecurity incident. It names who decides, who is called and what is recorded. This page, read on 16 November 2026, defines the term in plain words and shows a short excerpt. ## What is an incident response plan in plain words? An incident response plan is the document people open when something has gone wrong with their systems or data. It says who is in charge, what counts as an incident, what each person does first, and who has to be told. NIST SP 800-61 Rev. 3 describes it as the roadmap for the incident response capability. The roadmap sits under an incident response policy, which states management's commitment and scope, and above playbooks, which give step-by-step actions for one kind of incident. ## What does a plan excerpt look like? Here is a short excerpt from the severity section of the template, with fields left in brackets: Level 3 High. Criteria: a critical service is down or degraded, or sensitive data may have been exposed. Who is called: all roles in section 2 and legal counsel. First response target: [minutes]. The excerpt shows the style. It is a rule a tired person can apply, with a named owner and a time target. ## What is the difference between an event and an incident? An event is something observed in a system; an incident is an event, or a group of events, that has been declared against defined criteria. NIST CSF outcome DE.AE-08 reads: incidents are declared when adverse events meet the defined incident criteria. The plan must therefore say what the criteria are and who declares. In the template that is section 5. ## Where does the plan sit among other documents? The policy says what the organization commits to. The plan says how decisions are made. Playbooks and procedures say how to do the work. See the pages on [policy](/plans/incident-response-policy/), [playbooks](/plans/incident-response-plan-vs-playbook/) and [business continuity](/plans/incident-response-plan-vs-business-continuity-plan/). ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [Incident response roles and responsibilities](/plans/incident-response-roles-and-responsibilities/) - [Incident response severity levels](/plans/incident-response-severity-levels/) - [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 steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) - 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/what-is-an-incident-response-plan/ --- # How to create an incident response plan Guide, read 16 November 2026 **The short answer.** Create an incident response plan in five working sessions: agree scope and roles, set severity and declaration rules, list contacts and legal duties, write the actions by phase, then test it with a walkthrough. This page, read on 16 November 2026, gives the order, sentence-level drafting rules and the sources behind them. ## 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. 1. Scope, owner and roles (sections 1 and 2). 2. Severity and declaration (sections 4 and 5). 3. Contacts and notices (sections 3 and 10). 4. Actions by phase (sections 6 to 9 and 11 to 13). 5. 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](/plans/how-to-test-an-incident-response-plan/). ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [Incident response severity levels](/plans/incident-response-severity-levels/) - [What is an incident response plan?](/plans/what-is-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 steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - 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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/how-to-create-an-incident-response-plan/ --- # How to test an incident response plan Guide, read 16 November 2026 **The short answer.** Test an incident response plan by walking the people named in it through a realistic scenario at least once a year, timing each decision and recording the gaps. Also test restoring from backups. This page, read on 16 November 2026, sets out the method, an agenda and the rules that require testing. ## How do you test an incident response plan? Run a walkthrough with every role named in the plan at least once a year. Give the group a scenario, release facts in stages, and ask each person what they would do, who they would call and what they would record. Time the answers and note every point where someone had to guess. The NCSC offers Exercise in a Box, a free resource that helps organizations test and practice their response to different types of cyber attack, with set-up, planning, delivery and post-exercise activity. It also advises practicing restores from backups. ## What does an exercise agenda look like? A 90-minute agenda works for most teams. Spend 10 minutes on the scenario and ground rules, 60 minutes on three or four injects, and 20 minutes on findings. | Minutes | Item | Output | | --- | --- | --- | | 0 to 10 | Scenario and ground rules | Shared start point | | 10 to 25 | Inject 1: first report arrives | Declaration and severity decision | | 25 to 45 | Inject 2: data may be involved | Notice clock decisions, who is called | | 45 to 70 | Inject 3: press or customer question | Message approved by the communications lead | | 70 to 90 | Findings | Actions with owner and date | What does an exercise agenda look like? ## Which rules require testing? New York 23 NYCRR 500.16(d) requires covered entities to test incident response and business continuity plans with all staff and management critical to the response, and to test the ability to restore critical data from backups, at least annually. CISA's federal playbook calls for regular recovery exercises and annual continuity testing. In NIST terms, outcome ID.IM-02 covers improvements identified from security tests and exercises, including those done with suppliers and relevant third parties. ## What do you do with the findings? Record each gap as an action with an owner and a due date, and update the plan within 30 days. Add the supplier or regulator contacts that were missing. Re-run any step that failed. The [post-incident review section](/templates/incident-response-checklist-template/) of the template uses the same action format. ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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/) - [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 steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - 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) - 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) - 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/how-to-test-an-incident-response-plan/ --- # Incident response plan vs playbook Guide, read 16 November 2026 **The short answer.** An incident response plan sets roles, authorities, severity rules and notice duties for every incident. A playbook gives the actionable steps for one scenario, such as phishing. NIST SP 800-61 Rev. 3 notes that many organizations document procedures as playbooks. This page, read on 16 November 2026, shows where each belongs. ## What is the difference between an incident response plan and a playbook? The plan answers who decides and what applies to all incidents. A playbook answers what to do next in one scenario. NIST SP 800-61 Rev. 3 says playbooks provide actionable steps or tasks for people to perform during various scenarios or situations, and that formatting procedures as playbooks can improve their usability. The plan stays stable and short; playbooks change as tools and threats change, and there are several of them. ## What belongs in the plan and what moves to a playbook? Keep in the plan: roles, severity levels, declaration criteria, authority to contain, communication rules, legal notice duties and review. Move to playbooks: the ordered steps, tools and decision points for one scenario. | Content | Plan | Playbook | | --- | --- | --- | | Who may isolate a system | Yes | Refers to the plan | | Which logs to search for phishing | No | Yes | | Severity scale | Yes | Uses the scale | | Steps to reset a cloud account | No | Yes | | Regulator notice deadlines | Yes | Prompts a check | What belongs in the plan and what moves to a playbook? ## How does Microsoft structure a playbook? Microsoft's public incident response playbooks each include prerequisites, a workflow, a checklist and detailed investigation steps. They cover phishing, password spray, app consent grant, compromised and malicious applications, and token theft. The [playbook library](/playbooks/) uses the same four-part idea for eight incident types, and the [playbook template](/playbooks/incident-response-playbook-template/) is blank. ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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 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 steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-plan-vs-playbook/ --- # Incident response plan vs business continuity plan Guide, read 16 November 2026 **The short answer.** An incident response plan handles the security event: declaring, containing and recovering. A business continuity plan keeps critical operations running through any disruption. NIST advises synchronizing the two because incidents can undermine business resilience. This page, read on 16 November 2026, shows the hand-off points. ## What is the difference between an incident response plan and a business continuity plan? The incident response plan covers the security incident itself; the business continuity plan covers keeping the business running during disruption. NIST SP 800-61 Rev. 3 lists both among the plans relevant to incident response and says to synchronize business continuity plans with incident response plans, since incidents can undermine business resilience (CSF outcome ID.IM-04). The NCSC likewise says to link the incident response plan to disaster recovery, business continuity and crisis management plans, which come into play when an incident causes major disruption or damage. ## Where do the two plans hand off? The hand-off happens at declaration of a severity 3 or 4 incident and at the recovery decision. At declaration, the incident lead tells the continuity lead which services are affected. At recovery, the continuity plan sets the order of restoration and the minimum viable operation. | Moment | Incident response plan | Business continuity plan | | --- | --- | --- | | Service down | Contain and find cause | Switch to manual or backup process | | Recovery order | Confirms systems are clean | Sets business priority | | Communication | Regulators, customers on the incident | Staff, customers on service levels | | Exercise | Annual walkthrough | Joint scenario once a year | Where do the two plans hand off? ## Do the rules treat them together? Yes in at least one case. New York 23 NYCRR 500.16 requires written plans including incident response, business continuity and disaster recovery, and requires annual testing of the response and continuity plans and of the ability to restore from backups. NIST adds that business continuity planners may be valuable in planning responses to specific incident types, such as denial-of-service conditions. See the [DDoS playbook](/playbooks/incident-response-playbook-for-ddos-attack/). ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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 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 steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-plan-vs-business-continuity-plan/ --- # Incident response policy: what it is and who approves it Guide, read 16 November 2026 **The short answer.** An incident response policy is the short, approved statement of management commitment, scope, definitions, authorities and measures that sits above the plan. NIST lists its usual elements and says cybersecurity policies should include one. This page, read on 16 November 2026, gives the clauses and the approver question. ## What is an incident response policy? An incident response policy is the high-level statement that governs how an organization responds to incidents. NIST SP 800-61 Rev. 3 says most such policies include a statement of management commitment, purpose and objectives, scope, definitions of events and incidents, roles with authorities, guidelines for prioritizing and recovery, and performance measures. In CSF 2.0 terms, outcome GV.PO says cybersecurity policy is established, communicated and enforced; NIST's recommendation under it is that cybersecurity policies should include an incident response policy. ## What clauses should the policy carry? Use these seven clauses and keep the policy to one page. 1. Management commitment to a response capability. 2. Purpose and objectives. 3. Scope: to whom and what it applies, and when. 4. Definitions of event, incident and related terms. 5. Roles, responsibilities and authorities, including who may confiscate, disconnect or shut down technology assets. 6. Guidelines for prioritizing incidents, estimating severity and starting recovery. 7. Performance measures. ## Who approves the incident response policy? NIST does not name a single approver, because policy is individualized. Its CSF outcome GV.RR-01 says organizational leadership is responsible and accountable for cybersecurity risk, and GV.PO-01 says policy is established and communicated based on context and strategy. In practice the most senior leader accountable for cybersecurity risk signs, after consulting legal, human resources, IT and the business owners who bear the impact. Write the approver's title and the approval date in section 1 of the plan. The FTC Safeguards Rule adds that the Qualified Individual reports to the board at least annually. ## How is the policy different from the plan? The policy states commitments and authorities and changes rarely. The plan, covered on the [plan guide](/plans/), carries the working detail. See also [the template](/). ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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 roles and responsibilities](/plans/incident-response-roles-and-responsibilities/) - [Incident response severity levels](/plans/incident-response-severity-levels/) - [Incident response steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) - 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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-policy/ --- # Incident response roles and responsibilities Guide, read 16 November 2026 **The short answer.** An incident response team needs an executive sponsor, an incident lead, a technical lead, a communications lead, a legal and privacy lead, and support from human resources, physical security and system owners. NIST SP 800-61 Rev. 3 describes these role families. This page, read on 16 November 2026, gives each role's decisions. ## Who is on an incident response team? The team is a set of roles, not a department. NIST SP 800-61 Rev. 3, section 2.2, gives examples: leadership, incident handlers, technology professionals, legal, public affairs and media relations, human resources, physical security and facilities management, and asset owners. Incident handlers may be on staff, on contract, or available when needed. Small organizations often combine roles and use an outside provider for handlers; the plan should still name each role and a deputy. | Role | Decides | NIST role family | | --- | --- | --- | | Executive sponsor | Funding; shutting down or rebuilding critical services | Leadership | | Incident lead | Declaring and closing; priorities | Incident handlers | | Technical lead | Containment and recovery actions | Technology professionals | | Communications lead | Every message; spokesperson | Public affairs and media relations | | Legal and privacy lead | Notice duties and clocks; law enforcement contact | Legal | | Human resources | Cases involving employees | Human resources | | Facilities | Physical access to sites and devices | Physical security | | System and data owners | Recovery priority for their assets | Asset owners | Who is on an incident response team? ## What should be said about outside providers? NIST describes a shared responsibility model: the contract should define the provider's responsibilities, information flows, coordination and authority to act, including restrictions such as sharing sanitized incident information with other customers or deactivating services to contain an incident. Service providers can hold privileged access, so NIST advises considering the risk of malicious insiders or provider compromise, and using confidentiality agreements and contract clauses. ## How do you assign roles in a small team? Name one person per role even when the same person holds several, and name a deputy for each. Check that no single absence leaves a role empty. Print the table and put it in the plan, section 2 of the [template](/). For a business with no security staff, the [small business template](/templates/incident-response-plan-template-for-small-business/) reduces the roles to an incident lead, outside help and a decision-maker for money. ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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 severity levels](/plans/incident-response-severity-levels/) - [What is an incident response plan?](/plans/what-is-an-incident-response-plan/) - [Incident response steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-roles-and-responsibilities/ --- # Incident response severity levels Guide, read 16 November 2026 **The short answer.** Severity levels sort incidents by business impact so that the right people are called at the right speed. A four-level scale from low to critical works for most organizations. This page, read on 16 November 2026, gives the scale, who is called at each level, and how NIST and SANS treat prioritization. ## What severity levels should an incident response plan use? Use four levels: low, medium, high and critical. Define each by business impact, name who is called, and set a response target. Re-rate when facts change. NIST CSF outcome RS.MA-03 reads: incidents are categorized and prioritized, and DE.AE-04 says the estimated impact and scope of adverse events are understood. | Level | Criteria | Who is called | | --- | --- | --- | | 1 Low | One user or device; no sensitive data exposed; no service affected | Incident lead | | 2 Medium | More than one user or device, or a non-critical service affected | Incident lead, technical lead | | 3 High | A critical service down, or sensitive data may be exposed | All roles and legal counsel | | 4 Critical | Wide loss of service, confirmed regulated data exposure, or a safety threat | All roles, executive sponsor, outside responders | What severity levels should an incident response plan use? ## How does impact set the level? The SANS Incident Handler's Handbook gives an example: a single workstation being non-functional can be considered minor, a server being down could be moderate if there are backups for failover, and data stolen directly from human resources that contains privileged information could be high. It adds that ranking incident types by organizational impact helps build the case for management support. Add data sensitivity and legal duties to the criteria; a small breach of regulated data can be higher severity than a large outage. ## When should severity trigger escalation? NIST CSF outcome RS.MA-04 reads "Incidents are escalated or elevated as needed". The NCSC advises establishing criteria for escalation to senior management and for scaling up the response, based on what matters most to your organization. The [template](/) section 4 carries the table; the [roles page](/plans/incident-response-roles-and-responsibilities/) shows who is called. ## Related pages - [Incident response plan: what it contains and how to build one](/plans/) - [Free incident response plan template](/) - [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/) - [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/) - [Incident response steps: the order and who does what](/steps/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/plans/incident-response-severity-levels/ --- # Incident response steps: the order and who does what Steps, read 16 November 2026 **The short answer.** Incident response runs in five steps: prepare, detect and analyze, contain, eradicate and recover, then learn. CISA's playbook uses this order, which follows NIST SP 800-61 Rev. 2. This page, read on 16 November 2026, shows what each step must produce and who owns it, and links to the six-step and NIST views. ## What are the steps in incident response? The steps are prepare, detect and analyze, contain, eradicate and recover, and learn. CISA's Cybersecurity Incident & Vulnerability Response Playbooks (November 2021) organize the incident response process into preparation, detection and analysis, containment, eradication and recovery, and post-incident activities, with coordination across all of them. The same playbook says many activities are iterative and may occur continuously until the incident is closed out. The steps are therefore a guide to emphasis, not a strict line. | Step | Must produce | Owner in the template | | --- | --- | --- | | 1 Prepare | Approved plan, named roles, contacts, tested backups | Executive sponsor, incident lead | | 2 Detect and analyze | A declared incident with a scope and a severity | Incident lead, technical lead | | 3 Contain | Spread stopped; evidence preserved | Technical lead | | 4 Eradicate and recover | Threat removed; systems restored and verified | Technical lead, system owners | | 5 Learn | Report, root cause and dated actions | Incident lead | What are the steps in incident response? ## What happens in each step? Step 1, prepare. Document policy and plan, set up logging and detection, train responders and users, and agree communication channels. CISA lists establishing staffing plans and means of collecting forensic evidence. Step 2, detect and analyze. Declare the incident, determine scope, and collect and preserve data. CISA tells federal agencies to report every incident to CISA; for others the local legal duty applies. Step 3, contain. Isolate affected systems, block malicious access and change credentials where compromise is suspected, while keeping evidence. Step 4, eradicate and recover. Remove the threat, rebuild or reimage, then restore and test systems and watch for re-entry. Step 5, learn. Hold a review, finalize reports, adjust detections and update the plan. ## Which models use a different count of steps? NIST SP 800-61 Rev. 3 (April 2025) now ties incident response to the six CSF 2.0 Functions. The SANS Incident Handler's Handbook uses six phases. The [NIST versus SANS page](/steps/incident-response-steps-nist-vs-sans/) puts them side by side, and the [six-step page](/steps/incident-response-plan-6-steps/) describes the SANS model. See also the [correct order of the steps](/steps/correct-order-of-incident-response-steps/) and the [containment step](/steps/containment-step/). ## All step pages - [Incident response plan in 6 steps: the SANS model](/steps/incident-response-plan-6-steps/) - [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/) - [What is the correct order of incident response steps?](/steps/correct-order-of-incident-response-steps/) - [The containment step of incident response](/steps/containment-step/) ## Related pages - [Free incident response plan template](/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Incident response plan: what it contains and how to build one](/plans/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [The standards map](/standards-map/) ## Sources - 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) - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/ --- # Incident response plan in 6 steps: the SANS model Steps, read 16 November 2026 **The short answer.** The SANS six-step model runs preparation, identification, containment, eradication, recovery and lessons learned. It comes from the SANS Incident Handler's Handbook, published 21 February 2012. This page, read on 16 November 2026, gives each step's purpose and what it must leave behind. ## What are the six steps of incident response? The six steps are preparation, identification, containment, eradication, recovery and lessons learned. The SANS Incident Handler's Handbook says it limits itself to the six phases of the incident handling process and notes that each phase, from preparation to lessons learned, is best followed in sequence because each builds on the other. | Step | Purpose in the handbook | Leaves behind | | --- | --- | --- | | 1 Preparation | Ready the team: policy, response plan, communication, documentation, team, access control, tools, training | Plan, contact list, tools, drilled team | | 2 Identification | Detect and decide whether a deviation is an incident, and its scope | Declared incident, evidence, notified team | | 3 Containment | Limit damage: short-term containment, system back-up, long-term containment | Stopped spread, forensic image | | 4 Eradication | Remove and restore affected systems, usually by reimaging, and improve defenses | Clean systems, patched weakness | | 5 Recovery | Return systems to production carefully, test, monitor and validate | Systems back, monitored | | 6 Lessons learned | Complete documentation and review | Report, meeting, improvements | What are the six steps of incident response? ## What does preparation include in the SANS model? The handbook lists eight elements: policy, response plan or strategy, communication, documentation, the response team, access control, tools and training. It suggests a "jump bag" holding everything responders need and drills at regular intervals. Template sections 1 to 4, 12 and 14 cover the same ground. ## How quickly should lessons learned happen? The handbook says the lessons learned meeting should be held as soon as possible and gives a rule of thumb of within two weeks after the incident, with a short report and an executive summary. The template's [review section](/templates/incident-response-checklist-template/) uses a 10 business day default that you can change. ## Where does this model sit beside NIST? NIST SP 800-61 Rev. 3 maps the older four-phase NIST model to CSF 2.0 Functions. The SANS model splits NIST's "containment, eradication and recovery" phase into three. See [NIST versus SANS](/steps/incident-response-steps-nist-vs-sans/). ## Related pages - [Incident response steps: the order and who does what](/steps/) - [Free incident response plan template](/) - [What is the correct order of incident response steps?](/steps/correct-order-of-incident-response-steps/) - [The containment step of incident response](/steps/containment-step/) - [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/) - [Incident response plan: what it contains and how to build one](/plans/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/incident-response-plan-6-steps/ --- # Incident response steps: NIST vs SANS compared Steps, read 16 November 2026 **The short answer.** NIST SP 800-61 Rev. 2 used four phases, Rev. 3 (April 2025) maps response to the six CSF 2.0 Functions, SANS uses six phases and CISA uses five. They describe the same work. This page, read on 16 November 2026, sets them in one table and says how to choose. ## How do the NIST and SANS incident response steps compare? NIST and SANS describe the same work with different cuts. The older NIST model has four phases; SANS has six because it splits containment, eradication and recovery. NIST SP 800-61 Rev. 3 replaced the circular model with the six CSF 2.0 Functions: Govern, Identify, Protect, Detect, Respond and Recover. | Work | NIST Rev. 2 (previous) | NIST Rev. 3 CSF 2.0 | CISA playbook | SANS handbook | | --- | --- | --- | --- | --- | | Get ready | Preparation | Govern, Identify, Protect | Preparation | Preparation | | Find and decide | Detection and analysis | Detect | Detection and analysis | Identification | | Stop the spread | Containment, eradication and recovery | Respond (RS.MI-01) | Containment | Containment | | Remove the cause | Containment, eradication and recovery | Respond (RS.MI-02) | Eradication and recovery | Eradication | | Restore service | Containment, eradication and recovery | Recover | Eradication and recovery | Recovery | | Learn | Post-incident activity | Identify: Improvement (ID.IM) | Post-incident activities | Lessons learned | How do the NIST and SANS incident response steps compare? ## Why did NIST change the model? NIST Rev. 3 says that when the earlier model was written incidents were relatively rare and quick to resolve, but today they occur frequently and recovery often takes weeks or months. It says incident response is now a critical part of cybersecurity risk management and that lessons should be shared as soon as they are identified, not delayed until after recovery. The practical point: improvement runs through all the work and does not wait for the end. ## Which model should you choose? Use the CSF 2.0 layout if your organization already reports against the NIST Cybersecurity Framework; the [NIST layout template](/templates/incident-response-plan-template-nist/) groups the plan that way. Use the six SANS steps for team training and checklists, and the five CISA steps if you work with federal agencies. NIST advises organizations to use the lifecycle model that suits them best. Any of the models can sit behind the same plan text. ## Related pages - [Incident response steps: the order and who does what](/steps/) - [Free incident response plan template](/) - [The containment step of incident response](/steps/containment-step/) - [Incident response plan in 6 steps: the SANS model](/steps/incident-response-plan-6-steps/) - [What is the correct order of incident response steps?](/steps/correct-order-of-incident-response-steps/) - [Incident response plan: what it contains and how to build one](/plans/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/steps/incident-response-steps-nist-vs-sans/ --- # What is the correct order of incident response steps? Steps, read 16 November 2026 **The short answer.** The order is prepare, detect and analyze, contain, eradicate, recover, then learn, but the steps overlap. CISA says many activities are iterative, eradication and recovery can run at the same time, and new findings send responders back to analysis. This page, read on 16 November 2026, shows what runs in parallel. ## What is the correct order of incident response steps? Start with preparation, then detection and analysis, containment, eradication and recovery, and post-incident review. That order matches the CISA playbook and the SANS handbook. Preparation is not part of the incident itself; it happens before. NIST SP 800-61 Rev. 3 says the preparation activities of Govern, Identify and Protect are broader risk management activities that support incident response, which is the Detect, Respond and Recover work. ## Which steps run in parallel? Several do. CISA says eradication and recovery actions can be executed simultaneously. It says that if new signs of compromise appear during containment, responders return to the technical analysis step to re-scope the incident. After eradication, detection and analysis continue to watch for re-entry. Documentation and communication run through every step. - Evidence preservation starts at detection and continues until closure. - Communication starts at declaration and continues to the last update. - Lessons are shared as they appear, not only at the end, per NIST Rev. 3. - Legal notice clocks start at the point each rule defines and run in parallel with technical work. ## What must be true before moving to the next step? Use stage gates. Before eradication: all means of persistent access have been accounted for, the adversary activity is sufficiently contained and all evidence has been collected (CISA). Before recovery: the cause is removed and backups are verified. Before closing: the recovery exit criteria in the plan are met and documentation is complete (CSF outcome RC.RP-06). The [containment step](/steps/containment-step/) page covers the first gate in detail. | Gate | Test before moving on | | --- | --- | | Detect to contain | Incident declared, severity set, evidence preserved | | Contain to eradicate | No new signs of compromise; persistence accounted for; evidence collected | | Eradicate to recover | Cause removed; backups verified | | Recover to close | Systems verified; exit criteria met; documents complete | What must be true before moving to the next step? ## Related pages - [Incident response steps: the order and who does what](/steps/) - [Free incident response plan template](/) - [Incident response plan in 6 steps: the SANS model](/steps/incident-response-plan-6-steps/) - [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/) - [The containment step of incident response](/steps/containment-step/) - [Incident response plan: what it contains and how to build one](/plans/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) - 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) - 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/steps/correct-order-of-incident-response-steps/ --- # The containment step of incident response Steps, read 16 November 2026 **The short answer.** Containment stops an incident from spreading while keeping evidence. SANS splits it into short-term containment, a forensic system back-up and long-term containment. CISA lists isolating systems, blocking access and rotating credentials. This page, read on 16 November 2026, gives the choices and what to weigh. ## What is containment in incident response? Containment is the step that prevents further damage by removing the adversary's access or limiting the spread. CISA says its objective is to prevent further damage and reduce the immediate impact. NIST CSF outcome RS.MI-01 is: incidents are contained. The right approach depends on the scenario; CISA notes that containing an active adversary using fileless malware differs from containing ransomware. ## What are the three parts of containment in the SANS handbook? Short-term containment limits damage fast, for example by isolating a network segment or moving traffic to failover servers. System back-up takes a forensic image before any system is wiped. Long-term containment lets affected systems stay in production while clean ones are built, by removing attacker accounts and backdoors and patching. | Part | Example action | Why | | --- | --- | --- | | Short-term | Isolate a network segment; disconnect a device | Limit the damage at once | | System back-up | Forensic image of the affected system | Preserve evidence of what happened | | Long-term | Remove attacker accounts and backdoors; patch neighbors | Keep the business running while rebuilding | What are the three parts of containment in the SANS handbook? ## What does CISA list as containment activities? CISA lists isolating impacted systems and network segments, capturing forensic images, updating firewall filtering, blocking unauthorized access and malware sources, closing specific ports and servers, and changing administrator passwords and rotating private keys and service account secrets where compromise is suspected. It also says defenders should avoid "tipping off" the adversary, and that if new signs of compromise are found the response returns to technical analysis to re-scope. ## What should you weigh before each action? CISA tells responders to consider adverse impacts on mission operations and availability of services, the duration and effectiveness of containment, and the effect on evidence. The NCSC warns against over-reacting: it can cause more damage than the incident, and an attacker may bury deeper. Record who approved each action and when. Template section 7 has the decision table, on the [home page](/). ## Related pages - [Incident response steps: the order and who does what](/steps/) - [Free incident response plan template](/) - [Incident response steps: NIST vs SANS compared](/steps/incident-response-steps-nist-vs-sans/) - [What is the correct order of incident response steps?](/steps/correct-order-of-incident-response-steps/) - [Incident response plan in 6 steps: the SANS model](/steps/incident-response-plan-6-steps/) - [Incident response plan: what it contains and how to build one](/plans/) - [Incident response playbook: what it is and how to build a library](/playbooks/) ## Sources - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (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) - 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) - 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/steps/containment-step/ --- # Incident response playbook: what it is and how to build a library Guide, read 16 November 2026 **The short answer.** An incident response playbook is a set of actionable steps for one scenario, such as phishing or a lost laptop. NIST SP 800-61 Rev. 3 says many organizations document procedures as playbooks. This page, read on 16 November 2026, explains the idea and links to eight free playbooks and a blank template. ## What is an incident response playbook? An incident response playbook is a ready set of steps for one kind of incident. NIST SP 800-61 Rev. 3 says playbooks provide actionable steps or tasks for people to perform during various scenarios or situations, and points to CISA's federal playbooks as examples. Each playbook in this library has six parts: when to use it, prerequisites, a workflow, decision points, notices to check and exit criteria. ## Which playbooks should you write first? Write the playbooks for the incidents you are most likely to face. NIST says it is impossible to have detailed procedures for every situation, so organizations should document procedures for the most common types of incidents and threats, and for urgent processes such as redeploying the primary authentication platform. The library starts with eight types that the research behind this site found people asking for. - [Phishing incident playbook](/playbooks/incident-response-playbook-phishing/) - [Business email compromise playbook](/playbooks/business-email-compromise-playbook/) - [Malware incident playbook](/playbooks/malware-incident-response-playbook/) - [Insider incident playbook](/playbooks/insider-threat-incident-response-playbook/) - [Lost or stolen device playbook](/playbooks/lost-or-stolen-device-playbook/) - [Cloud account compromise playbook](/playbooks/cloud-account-compromise-playbook/) - [DDoS attack playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Third-party and supplier incident playbook](/playbooks/third-party-incident-response-playbook/) ## How do the playbooks connect to the plan? The [plan](/) gives roles, severity and notice duties; each playbook points back to it for those. Read [plan versus playbook](/plans/incident-response-plan-vs-playbook/) for the split. Ransomware has its own playbook elsewhere and is not covered here. Use the [blank template](/playbooks/incident-response-playbook-template/) to add your own. ## More on playbooks - [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/) - [How to write an incident response playbook](/playbooks/how-to-write-an-incident-response-playbook/) - [Incident response playbook template](/playbooks/incident-response-playbook-template/) - [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/) - [Business email compromise incident response playbook](/playbooks/business-email-compromise-playbook/) - [Malware incident response playbook](/playbooks/malware-incident-response-playbook/) - [Insider threat incident response playbook](/playbooks/insider-threat-incident-response-playbook/) - [Lost or stolen device incident response playbook](/playbooks/lost-or-stolen-device-playbook/) - [Cloud account compromise incident response playbook](/playbooks/cloud-account-compromise-playbook/) - [DDoS attack incident response playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/) ## Related pages - [Free incident response plan template](/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) - [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) - 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) - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/ --- # What is an incident response playbook, and what is it for? Guide, read 16 November 2026 **The short answer.** An incident response playbook is a step-by-step guide for one type of incident, used by whoever is on shift when it happens. Its purpose is speed and consistency under pressure. This page, read on 16 November 2026, defines the term, states its purpose and shows what a playbook must address. ## What is the purpose of an incident response playbook? A playbook exists so that the person on shift at 3 a.m. can act without reinventing the process. Microsoft says its playbooks help teams respond quickly to active attacks, contain impact and improve response consistency across common scenarios. CISA's federal playbook states when to use it, for example for confirmed malicious cyber activity involving lateral movement, credential access or data exfiltration, and when not to, for example a phishing email click with no compromise. ## What must an incident response playbook address? Every playbook should state its trigger, prerequisites, ordered actions, decision points and exit criteria. Microsoft's playbooks include prerequisites such as the logging to be turned on and the roles and permissions required, a workflow, a checklist and investigation steps. - Trigger: when to use it, and when not to. - Prerequisites: logs, access, tools. - Workflow: numbered steps, one owner each. - Decision points: who decides, on what facts. - Notices to check: legal clocks that may have started. - Exit criteria and follow-up. ## Why maintain playbooks? Tools and techniques change, so playbooks need an owner and a review date. Update a playbook after every incident or exercise that used it. NIST says procedures can be tested or exercised periodically to verify their accuracy and used to train new personnel. See [how to write a playbook](/playbooks/how-to-write-an-incident-response-playbook/) for the method, and [the library](/playbooks/) for eight examples. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [DDoS attack incident response playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/) - [How to write an incident response playbook](/playbooks/how-to-write-an-incident-response-playbook/) - [Incident response playbook template](/playbooks/incident-response-playbook-template/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/what-is-an-incident-response-playbook/ --- # How to write an incident response playbook Guide, read 16 November 2026 **The short answer.** Write a playbook by choosing one scenario, listing prerequisites, drafting a numbered workflow with an owner for each step, marking decisions, and testing it with someone who did not write it. This page, read on 16 November 2026, gives the method, a layout comparison and the sources. ## How do you write an incident response playbook? Follow six moves. First, name one scenario and its trigger. Second, list prerequisites: logs, access and tools. Third, write the workflow as numbered steps with one action and one role each. Fourth, mark each decision with who decides and on what facts. Fifth, list the notices to check. Sixth, define exit criteria. Then give the draft to a person who did not write it and watch them follow it. Fix every place they hesitate. 1. Name the scenario and trigger. 2. List prerequisites. 3. Draft the workflow. 4. Mark decision points. 5. List notices to check. 6. Set exit criteria, then test with a fresh reader. ## Which layout should a playbook use? Use a checklist for short procedures, a table where a decision needs several facts, and a flowchart where branches matter. Microsoft pairs a workflow diagram with a checklist for each playbook, noting the checklist can help in highly regulated environments to verify what has been done. | Layout | Best for | Limit | | --- | --- | --- | | Numbered checklist | Linear tasks such as phishing clean-up | Branches are awkward | | Table of decisions | Choices with several inputs | Needs a short key | | Flowchart | Branching investigations | Hard to read at 3 a.m. alone | Which layout should a playbook use? ## What is the difference between a playbook and a runbook? The sources read for this site define playbooks but do not define "runbook" as a separate term. NIST uses the words procedures and playbooks, and says procedures explain how technical processes are performed. A common practice is to keep the decision flow in the playbook and the tool commands in an attached procedure. Use the [blank template](/playbooks/incident-response-playbook-template/) to start, and compare with the [plan](/plans/incident-response-plan-vs-playbook/). ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/) - [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/) - [Incident response playbook template](/playbooks/incident-response-playbook-template/) - [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026) - Microsoft Learn, Phishing investigation playbook: https://learn.microsoft.com/en-us/security/operations/incident-response-playbook-phishing (read 16 November 2026) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/how-to-write-an-incident-response-playbook/ --- # Incident response playbook template Template, read 16 November 2026 **The short answer.** The blank incident response playbook template below has six parts: header, prerequisites, workflow, decision points, checklist and exit criteria. It is in full on this page and downloads as Word and PDF without sign-up. Read on 16 November 2026; the structure follows the layout of Microsoft's public playbooks. ## How do you use the incident response playbook template? Copy the six parts, fill the bracketed fields for one scenario, and store the result with the plan. Review each playbook every 12 months and after any incident that used it. The header names the owner and the review date. The workflow lists steps in order with one role each. The decision table records who decides and what each answer leads to. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-playbook-template.docx). PDF (40 KB): [download](/downloads/incident-response-playbook-template.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### Playbook header Fill in once per playbook. - Name: [incident type]. - Owner: [role]. Approved on [date]. Review every [12 months]. - Use when: [trigger in one sentence]. - Do not use when: [what belongs to another playbook]. ### Prerequisites What must be in place before an incident. - Logs to be on: [list]. - Access and roles responders need: [list]. - Tools and contacts: [list]. ### Workflow Numbered steps in order. One action per step. Name the role. 1. [Step 1: action, role, expected result] 2. [Step 2] 3. [Step 3] ### Decision points Each point where a person must decide. | Decision | Who decides | Information needed | If yes | If no | | --- | --- | --- | --- | --- | | [question] | [role] | [facts] | [next step] | [next step] | Decision points ### Checklist A tick-list that mirrors the workflow, for regulated settings. - [ ] [Step 1 done, time, by] - [ ] [Step 2 done, time, by] ### Exit criteria and follow-up When to close and what to update. - Exit when: [criteria]. - Update: [plan, detections, contacts]. - Review date: [date]. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/) - [How to write an incident response playbook](/playbooks/how-to-write-an-incident-response-playbook/) - [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/) - [Business email compromise incident response playbook](/playbooks/business-email-compromise-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/incident-response-playbook-template/ --- # Incident response playbook for phishing Playbook, read 16 November 2026 **The short answer.** The phishing playbook has six parts: when to use it, prerequisites, a five-stage workflow, decision points, notices to check and exit criteria. It follows Microsoft's phishing investigation stages. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 and checked against CISA and NCSC guidance. ## What is the incident response playbook for phishing? Phishing is one of the most common initial access techniques. Microsoft says a successful phishing attack can lead to credential compromise, malware execution, data exfiltration and lateral movement across identity, email and endpoint environments. CISA's October 2023 phishing guidance urges organizations to report phishing promptly to CISA at report@cisa.gov or its 24/7 line, and to file with the FBI IC3. The NCSC advises building a culture in which users report phishing without fear of blame, because users who fear reprisals will not report mistakes. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-phishing.docx). PDF (48 KB): [download](/downloads/incident-response-pb-phishing.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when staff report a suspicious message, or when a user clicked a link, opened a file or entered credentials after a message arrived by email, text or chat. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Mailbox auditing is on for all mailboxes, and message trace logs can be searched. - Sign-in logs and endpoint alerts are kept and searchable. - At least one identifier (email address or username) is known for each suspected target. - Staff know how to report a message with one click or one phone call, and know they will not be blamed. - Responders have the accounts and roles needed to search mail, reset sessions and remove messages. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Identify and confirm the phishing message: get the original message and its message identifier. 2. Scope: find every recipient and whether each message was delivered. 3. Assess interaction: who opened, clicked or replied, and who entered credentials or ran a file. 4. Look for follow-on activity: new sign-ins, mailbox rules, forwarding, file downloads, new devices, lateral movement. 5. Contain: remove the message from all mailboxes; block the sender, link and domain; revoke sessions and reset passwords for exposed accounts; isolate any device that ran a file. 6. Prevent recurrence: add detections, adjust filters, and send a short note to staff. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Is any account or device compromised? | Technical lead | Sign-in logs, endpoint alerts, user interview | | Is data exposed? | Technical lead, privacy lead | Mailbox access logs, downloads, forwarding rules | | Is this one message or a campaign? | Incident lead | Recipient count, similar messages elsewhere | | Is a payment request involved? | Incident lead | If yes, also open the business email compromise playbook | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If personal data was accessed, start the data breach plan and the clocks in section 10. - Report phishing to the national service for your country; CISA asks organizations to report to report@cisa.gov or its 24/7 line, and the FBI IC3 takes complaints. ### Exit criteria and follow-up Close the playbook only when all of these are true. - No malicious messages remain in any mailbox. - Every exposed account is reset and its sessions are revoked. - No new suspicious activity for [period]. - Detections and filters are updated, and staff are told the outcome. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [How to write an incident response playbook](/playbooks/how-to-write-an-incident-response-playbook/) - [Incident response playbook template](/playbooks/incident-response-playbook-template/) - [Business email compromise incident response playbook](/playbooks/business-email-compromise-playbook/) - [Malware incident response playbook](/playbooks/malware-incident-response-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - Microsoft Learn, Phishing investigation playbook: https://learn.microsoft.com/en-us/security/operations/incident-response-playbook-phishing (read 16 November 2026) - CISA, Phishing Guidance: Stopping the Attack Cycle at Phase One (October 2023): https://www.cisa.gov/sites/default/files/2023-10/Phishing%20Guidance%20-%20Stopping%20the%20Attack%20Cycle%20at%20Phase%20One_508c.pdf (read 16 November 2026) - NCSC, Phishing guidance for organizations: https://www.ncsc.gov.uk/guidance/phishing (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/incident-response-playbook-phishing/ --- # Business email compromise incident response playbook Playbook, read 16 November 2026 **The short answer.** The business email compromise playbook covers a fraudulent payment request, a taken-over mailbox and a funds recall. Its first step is to call the bank, then file with the FBI IC3. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 from IC3 and NCSC sources. ## What is the incident response playbook for business email compromise? The FBI IC3 describes business email compromise as a scam that targets businesses and individuals who perform transfer-of-funds requests. It reports 305,033 incidents and $55,499,915,582 in exposed dollar loss from October 2013 to December 2023. If you discover a fraudulent transfer, IC3 says time is of the essence: contact your financial institution at once, request a recall and file a complaint at ic3.gov whatever the amount. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-bec.docx). PDF (47 KB): [download](/downloads/incident-response-pb-bec.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when a payment request, bank detail change or invoice looks fraudulent, when an executive or supplier email account may be controlled by someone else, or when funds may have been sent to a fraudulent account. ### Before you start: prerequisites Complete these before an incident, as part of planning. - The finance team has a call-back procedure on a known number for any change of bank details. - The bank's fraud and recall contact is on the contact sheet, available 24 hours. - Mailbox rules and forwarding can be listed for any user. - Two-step sign-in is required on email accounts, preferably with phishing-resistant methods. ### Workflow Work in this order. Record each step and its time in the incident log. 1. If a payment was sent, call the bank immediately and ask for a recall and any indemnification documents. Time matters. 2. File a complaint with the FBI IC3 (ic3.gov) as soon as possible, whatever the amount, so that it can help banks and law enforcement try to freeze funds. 3. Find the account used: check the sender, reply-to address, look-alike domains, and mailbox rules or forwarding set by an intruder. 4. Contain: reset the password, revoke sessions, remove the intruder's rules and forwarding on every affected mailbox. 5. Verify any open payment requests by phone on a known number. 6. Search for other victims inside and outside the company, and warn customers and suppliers whose details were used. 7. Preserve the emails, headers and bank records. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Recall funds or accept the loss? | Finance lead, executive sponsor | Amount, bank guidance, time since the transfer | | Is personal data exposed from the mailbox? | Privacy lead | Mailbox contents and access logs | | Tell the insurer? | Executive sponsor | Policy terms; crime and cyber cover | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If personal information of employees or customers was in the compromised mailbox, treat it as a possible data breach. - Insurance notice may be required for both crime and cyber policies. ### Exit criteria and follow-up Close the playbook only when all of these are true. - Bank recall requested, and the IC3 complaint filed. - Intruder access removed from every mailbox. - The payment verification procedure is updated. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Incident response playbook template](/playbooks/incident-response-playbook-template/) - [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/) - [Malware incident response playbook](/playbooks/malware-incident-response-playbook/) - [Insider threat incident response playbook](/playbooks/insider-threat-incident-response-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - FBI IC3, Business Email Compromise: The $55 Billion Scam (11 September 2024): https://www.ic3.gov/PSA/2024/PSA240911 (read 16 November 2026) - NCSC, Phishing guidance for organizations: https://www.ncsc.gov.uk/guidance/phishing (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/business-email-compromise-playbook/ --- # Malware incident response playbook Playbook, read 16 November 2026 **The short answer.** The malware playbook covers validating an alert, isolating the device, checking for spread, imaging, reimaging and verified restore. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 from NCSC, CISA and SANS sources. Ransomware extortion decisions are outside its scope. ## What is the incident response playbook for malware? The NCSC says malware can cause harm in many ways: locking devices, stealing, deleting or encrypting data, taking control of devices, obtaining credentials and mining cryptocurrency. It stresses always having a recent offline backup of important data. CISA's eradication list includes reimaging affected systems from gold sources, rebuilding hardware where rootkits are involved, replacing compromised files with clean versions, installing patches and resetting passwords on compromised accounts. Ransomware extortion decisions are covered by other specialist guidance and not here. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-malware.docx). PDF (46 KB): [download](/downloads/incident-response-pb-malware.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when endpoint protection or a user reports malicious software on one or more devices. It excludes extortion cases, which are covered elsewhere. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Endpoint detection and response or antivirus alerts reach a monitored place. - Offline, tested backups exist for important data. - Responders can isolate a device remotely. - A clean rebuild image exists for each standard device. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Validate the alert and identify the device, user and malware family if known. 2. Short-term containment: isolate the device from the network. Do not power it off if memory evidence may be needed. 3. Check for spread: other devices with the same file, shared drives, and accounts used on the device. 4. Reset passwords and revoke sessions for any account that was used on the infected device. 5. Take a backup image of the affected system before wiping it. 6. Eradicate: reimage from a trusted source, replace compromised files with clean versions, and patch what was exploited. 7. Recover: restore data from a verified backup onto the clean system, and watch it for signs of re-infection. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Is this a single device or a spread? | Technical lead | Alerts, file hashes, network connections | | Rebuild or clean in place? | Technical lead | Malware type, risk of rootkits, time to rebuild | | Is data stolen? | Technical lead, privacy lead | Outbound traffic, staging files, cloud sync | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If data left the network, assess it under the data breach plan. - If the malware reached systems that run a service for customers, check customer contract notice terms. ### Exit criteria and follow-up Close the playbook only when all of these are true. - Malware removed from every device or the device rebuilt. - Credentials reset. - No new alerts for [period]. - The infection route is found and closed. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Incident response playbook for phishing](/playbooks/incident-response-playbook-phishing/) - [Business email compromise incident response playbook](/playbooks/business-email-compromise-playbook/) - [Insider threat incident response playbook](/playbooks/insider-threat-incident-response-playbook/) - [Lost or stolen device incident response playbook](/playbooks/lost-or-stolen-device-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - NCSC, Mitigating malware and ransomware attacks: https://www.ncsc.gov.uk/guidance/mitigating-malware-and-ransomware-attacks (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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/malware-incident-response-playbook/ --- # Insider threat incident response playbook Playbook, read 16 November 2026 **The short answer.** The insider threat playbook sets out how to handle suspected misuse of access by an employee or contractor, with human resources and legal involved from the start. It follows CISA's four steps. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026. ## What is the incident response playbook for an insider incident? CISA describes insider threat mitigation in four key steps: define, detect and identify, assess, and manage. It says detection is the process by which people who may present a risk through observable, concerning behaviors come to the attention of the organization or an insider threat team. NIST SP 800-61 Rev. 3 adds that human resources may be involved if an employee is suspected of intentionally causing an incident, and that legal experts advise where an incident may lead to prosecution or lawsuits. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-insider.docx). PDF (46 KB): [download](/downloads/incident-response-pb-insider.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when an employee, contractor or other trusted person is suspected of misusing access, whether on purpose or by mistake. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Human resources and legal have agreed in advance how an employee case is handled. - Access to sensitive systems is logged and reviewable. - A written policy tells staff what is acceptable and what is monitored, as the law in your location allows. - Responders know who may disable a person's access, and on whose authority. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Receive the concern and record it. Limit who knows to the people in the plan. 2. Involve human resources and legal before any action against a person. 3. Preserve evidence quietly: logs, mailbox, file access, device images where counsel agrees. 4. Assess against behavior and facts, not assumptions. CISA describes the steps as define, detect and identify, assess, and manage. 5. Contain access in a way the legal team has agreed, for example disabling accounts at the time of an interview. 6. Recover assets: devices, keys, tokens and data copies. 7. Decide actions with human resources and legal, and record them. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Is the act intentional or accidental? | Human resources, legal | Facts, intent indicators, history | | When to remove access? | Incident lead, human resources | Risk of further harm versus risk to evidence | | Involve law enforcement? | Legal counsel, executive sponsor | Nature of the act, data involved | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If personal data left the organization, assess it under the data breach plan. - Employment law may limit what can be monitored and what can be said. ### Exit criteria and follow-up Close the playbook only when all of these are true. - Access removed and assets recovered. - Evidence stored under legal direction. - Controls changed to reduce the chance of a repeat. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Business email compromise incident response playbook](/playbooks/business-email-compromise-playbook/) - [Malware incident response playbook](/playbooks/malware-incident-response-playbook/) - [Lost or stolen device incident response playbook](/playbooks/lost-or-stolen-device-playbook/) - [Cloud account compromise incident response playbook](/playbooks/cloud-account-compromise-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - CISA, Insider Threat Mitigation: https://www.cisa.gov/topics/physical-security/insider-threat-mitigation (read 16 November 2026) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/insider-threat-incident-response-playbook/ --- # Lost or stolen device incident response playbook Playbook, read 16 November 2026 **The short answer.** The lost device playbook covers locking or wiping the device, revoking sessions, finding what it held and deciding whether the loss is a reportable breach, which often turns on encryption. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026. ## What is the incident response playbook for a lost device? The U.S. Department of Education PTAC lists lost, stolen or temporarily misplaced equipment among the forms a data breach can take. Whether a lost device is a reportable breach often turns on encryption. HIPAA defines unsecured protected health information by whether it was rendered unusable, unreadable or indecipherable to unauthorized persons; GDPR Article 34(3)(a) removes the duty to tell individuals when the data was protected by measures such as encryption that made it unintelligible. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-lost-device.docx). PDF (46 KB): [download](/downloads/incident-response-pb-lost-device.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when a laptop, phone, tablet, removable drive or paper record that holds business data is lost, stolen or misplaced. ### Before you start: prerequisites Complete these before an incident, as part of planning. - A current asset list says which devices hold which data. - Devices are encrypted, and the list shows which ones are. - Remote lock and wipe is set up and tested for phones and laptops. - Staff know to report a loss at once, at any hour. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Record when and where the loss was noticed, when it was last seen, and who had it. 2. Lock or wipe the device remotely and revoke its sessions, tokens and certificates. 3. Reset passwords for accounts that were signed in on the device. 4. Find out what was on the device and whether it was encrypted and locked. 5. Check logs for sign-in attempts from the device after the loss. 6. If it may have been stolen, report to the police and record the report number. 7. Decide whether this is a reportable breach, using the encryption facts. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Was the data protected by encryption? | Technical lead | Device encryption status and key handling | | Is it a reportable breach? | Privacy lead, legal | Data types, people affected, rules in section 10 | | Wipe now or wait? | Technical lead | Chance of recovery versus risk of access | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - Under HIPAA, only unsecured protected health information triggers breach notice; the rule defines it by whether the information was rendered unusable, unreadable or indecipherable. - Under GDPR Article 34, communication to individuals is not required if the data was protected by measures such as encryption that made it unintelligible to unauthorized people. ### Exit criteria and follow-up Close the playbook only when all of these are true. - The device is recovered or wiped, and sessions revoked. - The reportability decision is recorded with reasons. - The asset list is corrected. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Malware incident response playbook](/playbooks/malware-incident-response-playbook/) - [Insider threat incident response playbook](/playbooks/insider-threat-incident-response-playbook/) - [Cloud account compromise incident response playbook](/playbooks/cloud-account-compromise-playbook/) - [DDoS attack incident response playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - 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) - eCFR, 45 CFR 164.402, Definitions (breach, unsecured protected health information): https://www.ecfr.gov/current/title-45/section-164.402 (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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/lost-or-stolen-device-playbook/ --- # Cloud account compromise incident response playbook Playbook, read 16 November 2026 **The short answer.** The cloud account compromise playbook covers revoking sessions, resetting credentials, reviewing application consents, rotating secrets and checking other accounts for password spray. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 from Microsoft and CISA sources. ## What is the incident response playbook for cloud account compromise? Microsoft publishes investigation playbooks for password spray, app consent grants, compromised and malicious applications, and token theft. The app consent playbook names the Application Administrator and Cloud Application Administrator roles as able to grant consent on behalf of the organization, and flags risky permissions such as Mail.* and Contacts.*. CISA's containment guidance includes changing administrator passwords, rotating private keys and service or application account secrets where compromise is suspected. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-cloud-account.docx). PDF (46 KB): [download](/downloads/incident-response-pb-cloud-account.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when a cloud identity, such as a user, administrator, service account or application, is used by someone other than its owner. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Sign-in and audit logs are on and retained in the cloud tenant. - The accounts that can grant application consent are known and limited. - Two-step sign-in is required, with phishing-resistant methods for administrators. - A break-glass administrator account exists and is stored securely. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Identify the account, the time window and the indicators: unusual sign-ins, impossible travel, new devices, new mailbox rules, new application consents. 2. Contain: revoke sessions and tokens, reset the password and require a fresh two-step enrollment. 3. Review application consents granted by the user or tenant-wide, and remove any suspicious application. Check permissions such as read and send mail. 4. Rotate administrator passwords, private keys and service account secrets where compromise is suspected. 5. Review what the account could reach and what it did: mail, files, configuration changes, new accounts. 6. Check other accounts for the same pattern, such as a password spray across many users. 7. Restore changed settings and add detections for the technique. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Is it one account or many? | Technical lead | Sign-in patterns across accounts | | Was an administrator account used? | Technical lead, executive sponsor | Role assignments, configuration changes | | Was data accessed or sent out? | Privacy lead | Audit logs, downloads, forwarding | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If personal data was accessed, start the data breach plan. - If the cloud provider is a processor for your customers, check section 12 and customer notice terms. ### Exit criteria and follow-up Close the playbook only when all of these are true. - All sessions and tokens revoked; credentials rotated. - No suspicious application consents remain. - Detections are in place for the technique used. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Insider threat incident response playbook](/playbooks/insider-threat-incident-response-playbook/) - [Lost or stolen device incident response playbook](/playbooks/lost-or-stolen-device-playbook/) - [DDoS attack incident response playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - Microsoft Learn, Password spray investigation: https://learn.microsoft.com/en-us/security/operations/incident-response-playbook-password-spray (read 16 November 2026) - Microsoft Learn, App consent grant investigation: https://learn.microsoft.com/en-us/security/operations/incident-response-playbook-app-consent (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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/cloud-account-compromise-playbook/ --- # DDoS attack incident response playbook Playbook, read 16 November 2026 **The short answer.** The DDoS playbook covers confirming an attack, classifying it as volumetric, protocol or application, calling the upstream provider, filtering and keeping customers informed. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 from CISA, FBI and NCSC sources. ## What is the incident response playbook for a DDoS attack? CISA, the FBI and MS-ISAC's guide of 21 March 2024 sorts denial-of-service techniques into volumetric, protocol and application types. It lists symptoms including website unavailability, network congestion, unusual traffic patterns, server crashes and high resource use. The NCSC's DoS guidance sets out four practices: understand your service, understand your defenses, create a response plan, and test your response. NIST adds that continuity planners may help plan responses to denial-of-service conditions. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-ddos.docx). PDF (46 KB): [download](/downloads/incident-response-pb-ddos.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when a website, application or network service becomes slow or unavailable because of a flood of traffic or requests. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Normal traffic baselines are known. - Contacts at the internet provider, content delivery network and any DDoS mitigation service are on the contact sheet. - The service has redundancy, load balancing and a way to scale. - Communications for customers are ready, with a way to post status away from the affected service. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Confirm it is an attack: check for unavailability, network congestion, unusual traffic patterns, server crashes, high resource use and trouble reaching other services such as DNS. 2. Classify the technique: volumetric, protocol or application. The response differs by type. 3. Call the upstream provider or mitigation service and ask for filtering. 4. Apply filtering at the edge: rate limits, blocks on known malicious sources, and a challenge for web requests where suitable. 5. Keep customers informed through a channel that does not depend on the affected service. 6. After the attack: assess the impact, restore services, do a post-incident analysis, fix what was found and update the plan. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Switch to a mitigation service or failover? | Technical lead, executive sponsor | Attack type, cost, time to switch | | Is the attack covering something else? | Incident lead | Other alerts, access attempts during the attack | | What do we tell customers? | Communications lead | Impact, expected recovery time | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - A DDoS attack alone is an availability incident; check whether personal data was affected before treating it as a breach. - Check contract service levels and customer notice terms. ### Exit criteria and follow-up Close the playbook only when all of these are true. - Service restored to normal levels. - Traffic patterns back to baseline for [period]. - The plan is updated with what was learned. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Lost or stolen device incident response playbook](/playbooks/lost-or-stolen-device-playbook/) - [Cloud account compromise incident response playbook](/playbooks/cloud-account-compromise-playbook/) - [Third-party and supplier incident response playbook](/playbooks/third-party-incident-response-playbook/) - [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## Sources - CISA, FBI and MS-ISAC, Understanding and Responding to Distributed Denial-of-Service Attacks (21 March 2024): https://www.cisa.gov/sites/default/files/publications/understanding-and-responding-to-ddos-attacks_508c.pdf (read 16 November 2026) - NCSC, Denial of Service (DoS) guidance: https://www.ncsc.gov.uk/collection/denial-service-dos-guidance-collection (read 16 November 2026) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/incident-response-playbook-for-ddos-attack/ --- # Third-party and supplier incident response playbook Playbook, read 16 November 2026 **The short answer.** The third-party playbook covers getting facts from a supplier, checking your logs, suspending access, rotating shared secrets and working out which notice clocks start. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026 from NIST, NCSC, GDPR and HIPAA sources. ## What is the incident response playbook for a third-party incident? NIST SP 800-61 Rev. 3 lists CSF outcome GV.SC-08: relevant suppliers and other third parties are included in incident planning, response, and recovery activities. It adds that responsibilities should be defined in the contract. The NCSC supply chain security guidance, published 28 January 2018 and reviewed 22 October 2025, sets out 12 principles and notes that very few UK businesses set minimum security standards for their suppliers, citing the 2025 Security Breaches Survey. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-pb-third-party.docx). PDF (46 KB): [download](/downloads/incident-response-pb-third-party.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### When to use this playbook Use this playbook when a supplier tells you it has been compromised, when a supplier's product or update is malicious, or when a supplier holding your data may have lost control of it. ### Before you start: prerequisites Complete these before an incident, as part of planning. - Each critical supplier is on the list in section 12 with an incident contact and a contractual notice time. - Contracts say what the supplier must tell you, how fast, and what it may do on your behalf. - You know what data and access each supplier has. - You have an exercise scenario that includes a supplier failure. ### Workflow Work in this order. Record each step and its time in the incident log. 1. Get the facts from the supplier: what happened, when, what of yours is affected, and what it has done. 2. Check your own logs for activity linked to the supplier: connections, API calls, accounts and updates. 3. Contain: suspend the supplier's access, rotate shared secrets and credentials, and block affected components. 4. Assess your exposure: data held by the supplier, access it had to your systems, and customers who depend on it. 5. Decide who must be told. A supplier that is a processor must tell you without undue delay under GDPR Article 33(2); a business associate must tell the covered entity under 45 CFR 164.410. 6. Agree a shared communications line with the supplier. 7. Review the contract and the supplier's assurance after the incident. ### Decision points Stop at each of these and record the decision, the decider and the time. | Decision | Who decides | Information needed | | --- | --- | --- | | Suspend the supplier's access? | Technical lead, executive sponsor | Risk to your systems versus the business use | | Are you the controller or covered entity with a notice duty? | Privacy lead, legal | Contract role, data involved | | Switch suppliers? | Executive sponsor | Alternatives, time to switch | Decision points ### Notices to check Open section 10 of the plan and confirm whether any of these start a notice clock. - If you are the controller or covered entity, your own clock may have started when the supplier told you, or earlier if you would have known with reasonable diligence. - Check customer contracts: your customers may expect notice because of your supplier's incident. ### Exit criteria and follow-up Close the playbook only when all of these are true. - Supplier access restored on agreed terms or ended. - Shared secrets rotated. - Contract and assurance updated. ## Related pages - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Free incident response plan template](/) - [Cloud account compromise incident response playbook](/playbooks/cloud-account-compromise-playbook/) - [DDoS attack incident response playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [What is an incident response playbook, and what is it for?](/playbooks/what-is-an-incident-response-playbook/) - [How to write an incident response playbook](/playbooks/how-to-write-an-incident-response-playbook/) - [Incident response plan templates: the full set](/templates/) - [Incident response steps: the order and who does what](/steps/) ## 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, Supply chain security guidance: https://www.ncsc.gov.uk/collection/supply-chain-security (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.410, Notification by a business associate: https://www.ecfr.gov/current/title-45/section-164.410 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/playbooks/third-party-incident-response-playbook/ --- # Incident response plan template for small business Template, read 16 November 2026 **The short answer.** The incident response plan template for small business fits on a few pages and follows the NCSC five steps: prepare, identify, resolve, report and learn. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026. It needs no security staff. ## What does an incident response plan for a small business need? A small business needs a named lead, outside help on call, tested backups, a short list of what counts as an incident, a first-hour routine and a list of who to tell. The NCSC Small Business Guide: Response & Recovery organizes this as five steps: prepare for incidents, identify what is happening, resolve the incident, report to wider stakeholders, and learn from the incident. ## What counts as a cyber incident for a small business? The NCSC defines a cyber incident as unauthorized access, or attempted access, to an organization's IT systems. It can be malicious, such as denial of service, malware, ransomware or phishing, or accidental, such as damage from fire, flood or theft. The NCSC says a business, charity or other organization suffering a live attack in the UK can call 0300 123 2040, a service available 24 hours a day, 7 days a week. Outside the UK, use the national reporting service for your country. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-small-business.docx). PDF (45 KB): [download](/downloads/incident-response-small-business.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Prepare: who is in charge Write this page once and print it. - Incident lead: [name], phone [number]. Deputy: [name], phone [number]. - Outside help: [IT provider or incident response firm], phone [number]. Insurance hotline: [number], policy [number]. - Where the backups are and who can restore them: [location and name]. Test a restore once a year. - The three systems we cannot run without: [system 1], [system 2], [system 3]. ### 2. Identify: what counts as an incident Call the incident lead if any of these happen. - Someone clicked a link or opened a file and the device now behaves oddly. - A password or account was shared, guessed or used by someone else. - A device with business data is lost or stolen. - A payment request or bank detail change looks wrong. - A website, system or phone line stops working and the cause is not clear. - A supplier or customer tells us they were breached. ### 3. Resolve: the first hour The incident lead does these in order and writes the time next to each. 1. Write down what you know: who, what, when, which devices and accounts. 2. Disconnect affected devices from the network. Do not delete anything. 3. Change passwords on affected accounts from a device you trust, and turn on two-step sign-in. 4. Call the outside help number on page 1 and tell the insurer if the policy requires it. 5. If money was sent, call the bank immediately and ask for a recall. 6. Decide with the outside help what to restore, and from which backup. ### 4. Report: who to tell and when Decide with legal advice whether any law or contract requires a notice, and how soon. | Who | When | Who tells them | Done (time) | | --- | --- | --- | --- | | Staff | After the first hour | [name] | | | Customers or partners affected | As soon as facts are confirmed | [name] | | | Regulator or authority, if any law applies | [deadline from the law] | [name] | | | Insurer | [per policy] | [name] | | | Police or national reporting service | If a crime, or funds were lost | [name] | | 4. Report: who to tell and when ### 5. Learn: after the incident Within two weeks, meet for 30 minutes. - What happened, in a few sentences. - What we did well. What we missed. - Three fixes, each with a name and a date. - Update this plan and the phone numbers. ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response checklist template](/templates/incident-response-checklist-template/) - [Incident response plan template: Word and PDF downloads](/templates/incident-response-plan-template-word-pdf/) - [Incident response plan template based on NIST](/templates/incident-response-plan-template-nist/) - [Incident response plan template for healthcare](/templates/incident-response-plan-template-healthcare/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - NCSC, Small Business Guide: Response & Recovery: https://www.ncsc.gov.uk/collection/small-business-guidance--response-and-recovery (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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-for-small-business/ --- # Incident response plan template based on NIST Template, read 16 November 2026 **The short answer.** NIST SP 800-61 Rev. 3, published April 2025, is a CSF 2.0 Community Profile, not a fill-in form. This template regroups the plan under the CSF Functions Govern, Identify, Detect, Respond and Recover and shows the outcome codes each section answers. Read on 16 November 2026. Word and PDF are free. ## Is there an incident response plan template based on NIST? NIST has not published a fill-in template for SP 800-61 Rev. 3. The publication is titled "Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile" and gives recommendations against CSF outcomes. This page arranges the same plan text under those Functions. Each section below ends with the outcome codes it answers, for example RS.MA-03 (incidents are categorized and prioritized). The full list with ISO/IEC 27001 control numbers is on the [standards map](/standards-map/). ## How does the NIST layout differ from the general template? The content is identical; only the order and headings change. Govern and Identify sections come first because they are preparation. Detect, Respond and Recover follow, and improvement closes the plan. NIST says lessons learned should be fed into improvement continuously, so the review section sits under the Improvement category ID.IM. Use the [general template](/) if your team does not report against CSF. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-nist-layout.docx). PDF (77 KB): [download](/downloads/incident-response-nist-layout.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### Govern (GV) and Identify (ID): prepare **1. Purpose, scope and authority** This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. CSF 2.0 outcomes answered: GV.PO-01, GV.PO-02, ID.IM-04, GV.RR-02. **2. Roles and responsibilities** Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. CSF 2.0 outcomes answered: GV.RR-01, GV.RR-02, PR.AT-02. **10. Legal, regulatory, contractual and insurance notices** List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. CSF 2.0 outcomes answered: GV.OC-03, RS.CO-02. **14. Testing, training and keeping the plan current** A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. CSF 2.0 outcomes answered: ID.IM-02, ID.IM-04, PR.AT-02, GV.PO-02. ### Detect (DE): find and declare **5. Detecting, reporting and declaring an incident** Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. CSF 2.0 outcomes answered: DE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-02. ### Respond (RS): manage, analyze, communicate and mitigate **6. Triage and analysis** Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. CSF 2.0 outcomes answered: RS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-04. **4. Severity levels** Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. CSF 2.0 outcomes answered: RS.MA-03, DE.AE-04, RS.AN-08. **3. Contact and escalation sheet** Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet CSF 2.0 outcomes answered: RS.CO-02, RS.CO-03, GV.SC-08. **11. Evidence handling and documentation** Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. CSF 2.0 outcomes answered: RS.AN-06, RS.AN-07. **12. Third parties and suppliers** List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. CSF 2.0 outcomes answered: GV.SC-08, DE.CM-06, RS.MA-01. **7. Containment** The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. CSF 2.0 outcomes answered: RS.MI-01, RS.MA-04. **9. Communications** One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." CSF 2.0 outcomes answered: RS.CO-02, RS.CO-03, RC.CO-03, RC.CO-04. ### Recover (RC): restore **8. Eradication and recovery** Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. CSF 2.0 outcomes answered: RS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-06. ### Improve (ID.IM): learn **13. Post-incident review** Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. CSF 2.0 outcomes answered: ID.IM-03, ID.IM-04, RC.RP-06. **Appendices: forms** Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms CSF 2.0 outcomes answered: RS.AN-06, RC.RP-06. ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template: Word and PDF downloads](/templates/incident-response-plan-template-word-pdf/) - [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) - [Incident response plan template for healthcare](/templates/incident-response-plan-template-healthcare/) - [Incident response plan template for financial services](/templates/incident-response-plan-template-financial-services/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## 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) - 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/templates/incident-response-plan-template-nist/ --- # Incident response plan template for healthcare Template, read 16 November 2026 **The short answer.** The health care incident response plan template adds the HIPAA Breach Notification Rule to the general plan: a four-factor risk assessment, individual notice within 60 days, notice to HHS and, over 500 residents of a State, to media. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does an incident response plan for health care need? A health care plan needs everything in the general plan plus a breach decision step and four notice paths. Under 45 CFR 164.402 an impermissible use or sharing of protected health information is presumed a breach unless a risk assessment shows a low probability of compromise. Notice runs to individuals within 60 calendar days of discovery, to the HHS Secretary (at the same time as the individual notice for 500 or more individuals; within 60 days after the end of the calendar year for fewer), and to media where more than 500 residents of a State are affected. A business associate must tell the covered entity within 60 days. The addendum below carries each with its source. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-healthcare.docx). PDF (78 KB): [download](/downloads/incident-response-healthcare.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. Health care: HIPAA breach notification Use this addendum if your organization is a HIPAA covered entity or a business associate. It adds the notice duties of the HIPAA Breach Notification Rule to section 10. - Record the date and time of discovery in the incident log, because the 60-day period counts from it. - Record whether the data was encrypted to the standard that makes it "secured". Only unsecured protected health information triggers these notices. - The individual notice must include: what happened with dates, the types of information involved, steps individuals should take, what the entity is doing, and contact procedures that include a toll-free number, an email address, a website or a postal address (164.404(c)). - A business associate adds the covered entity's incident contact to the contact sheet and the time allowed by the contract, which may be shorter than 60 days. | Duty | What the rule says | Deadline | Source | | --- | --- | --- | --- | | Presumption of breach | An impermissible use or sharing of protected health information is presumed a breach unless a risk assessment shows a low probability of compromise. The assessment weighs four factors: the nature and extent of the information, the person who used or received it, whether it was actually acquired or viewed, and how far the risk was mitigated. | Decide before the notice clock questions arise | 45 CFR 164.402 | | Notice to individuals | Notify each individual affected by a breach of unsecured protected health information, in plain language, by first-class mail or by email if the person agreed. | Without unreasonable delay and no later than 60 calendar days after discovery | 45 CFR 164.404 | | When a breach is "discovered" | The first day the breach is known, or would have been known with reasonable diligence, to the covered entity. | Start the clock on that day | 45 CFR 164.404(a)(2) | | Notice to the Secretary of HHS | 500 or more individuals: notify at the same time as individuals. Fewer than 500: keep a log and notify within 60 days after the end of the calendar year. | Same time, or 60 days after year end | 45 CFR 164.408 | | Notice to media | More than 500 residents of a State or jurisdiction: notify prominent media outlets serving that area. | No later than 60 calendar days after discovery | 45 CFR 164.406 | | Business associate to covered entity | A business associate notifies the covered entity of a breach it discovers. | Without unreasonable delay and no later than 60 calendar days after discovery | 45 CFR 164.410 | 10A. Health care: HIPAA breach notification ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) - [Incident response plan template based on NIST](/templates/incident-response-plan-template-nist/) - [Incident response plan template for financial services](/templates/incident-response-plan-template-financial-services/) - [Incident response plan template for public companies](/templates/incident-response-plan-template-public-company/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - eCFR, 45 CFR 164.402, Definitions (breach, unsecured protected health information): https://www.ecfr.gov/current/title-45/section-164.402 (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) - eCFR, 45 CFR 164.406, Notification to the media: https://www.ecfr.gov/current/title-45/section-164.406 (read 16 November 2026) - eCFR, 45 CFR 164.408, Notification to the Secretary: https://www.ecfr.gov/current/title-45/section-164.408 (read 16 November 2026) - eCFR, 45 CFR 164.410, Notification by a business associate: https://www.ecfr.gov/current/title-45/section-164.410 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-healthcare/ --- # Incident response plan template for financial services Template, read 16 November 2026 **The short answer.** The financial services incident response plan template maps to the FTC Safeguards Rule, which lists seven areas a written plan must address, and to New York 23 NYCRR 500.16, which adds nine areas and an annual test. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What must a financial services incident response plan cover? The FTC Safeguards Rule, 16 CFR 314.4(h), requires a written plan that addresses seven areas: goals; internal processes; roles, responsibilities and decision-making authority; communications and information sharing; remediation of weaknesses; documentation and reporting; and revision after a security event. New York 23 NYCRR 500.16 requires nine areas, including recovery from backups and a root cause analysis, and requires annual testing of the plan and of backup restores. Notice runs to the FTC within 30 days for events involving 500 or more consumers, and to the New York superintendent within 72 hours of determining an incident occurred. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-financial.docx). PDF (79 KB): [download](/downloads/incident-response-financial.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. Financial services: GLBA Safeguards Rule and New York 23 NYCRR 500 Use this addendum if your organization is a financial institution under the FTC's Safeguards Rule, or a covered entity under the New York Department of Financial Services cybersecurity regulation. The two rules prescribe what the plan must cover. - Add the seven Safeguards Rule areas as a checklist on the cover page of the plan and name the section of this plan that answers each. - Name the Qualified Individual in the roles table and schedule the annual board report. - For New York covered entities, add the root cause analysis template to appendix D and the backup restore test to the annual calendar. - Record the time the entity "determined" an incident occurred, because the 72-hour period counts from it. | Duty | What the rule says | Deadline | Source | | --- | --- | --- | --- | | Written incident response plan | Establish a written plan designed to respond to and recover from any security event materially affecting customer information. It must address seven areas: goals; internal processes; roles, responsibilities and levels of decision-making authority; external and internal communications and information sharing; remediation of identified weaknesses; documentation and reporting; and evaluation and revision after a security event. | In place now | 16 CFR 314.4(h) | | Notice to the FTC | If a notification event involves the information of at least 500 consumers, notify the FTC electronically. | As soon as possible and no later than 30 days after discovery | 16 CFR 314.4(j) | | Report to the board | The Qualified Individual reports in writing at least annually to the board or equivalent, covering program status and material matters, including security events and management's responses. | At least annually | 16 CFR 314.4(i) | | New York plan content | Plans must address nine areas: the same topics as the Safeguards Rule, plus recovery from backups and a root cause analysis describing how and why the event occurred, its business impact and what will prevent a repeat, with the plan updated as necessary. | In place now | 23 NYCRR 500.16(a)(1) | | New York test | Test the incident response and business continuity plans with all staff and management critical to the response, and test the ability to restore critical data from backups, at least annually. | At least annually | 23 NYCRR 500.16(d) | | Notice to the New York superintendent | Notify the superintendent electronically of a cybersecurity incident at the covered entity, its affiliates or a third-party service provider. | As promptly as possible and no later than 72 hours after determining an incident occurred | 23 NYCRR 500.17(a) | 10A. Financial services: GLBA Safeguards Rule and New York 23 NYCRR 500 ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template based on NIST](/templates/incident-response-plan-template-nist/) - [Incident response plan template for healthcare](/templates/incident-response-plan-template-healthcare/) - [Incident response plan template for public companies](/templates/incident-response-plan-template-public-company/) - [Incident response plan template for SaaS and technology companies](/templates/incident-response-plan-template-saas/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) - 23 NYCRR 500.17, Notices to superintendent (Cornell LII): https://www.law.cornell.edu/regulations/new-york/23-NYCRR-500.17 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-financial-services/ --- # Incident response plan template for public companies Template, read 16 November 2026 **The short answer.** The public company incident response plan template adds the SEC Form 8-K Item 1.05 duty to the general plan: decide materiality without unreasonable delay, then file within four business days of determining an incident is material. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does an incident response plan need for SEC Form 8-K Item 1.05? The plan needs a named owner of the materiality decision, a standing route to brief that owner, and a record of when the determination was made. SEC release 33-11216, effective September 5, 2023, requires a Form 8-K Item 1.05 filing for a material cybersecurity incident within four business days of determining that the incident was material. The release says registrants must make the determination without unreasonable delay. It lets the Attorney General delay filing if immediate public filing would pose a substantial risk to national security or public safety. Confirm the current text with securities counsel. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-public-company.docx). PDF (78 KB): [download](/downloads/incident-response-public-company.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. U.S. public companies: SEC Form 8-K Item 1.05 Use this addendum if your company files reports under the Securities Exchange Act of 1934. It adds the material cybersecurity incident filing to section 10. - Name who makes the materiality call (for example the committee that reviews public filings) and when the incident lead must brief them. - Add a standing agenda item: "Has anything changed that bears on materiality?" at each response meeting. - Record the date and time the determination was made, because the four business days count from it, not from discovery. - The rules took effect on September 5, 2023. Confirm the current text with securities counsel before relying on this summary. | Duty | What the rule says | Deadline | Source | | --- | --- | --- | --- | | Materiality determination | Registrants must make the materiality determination about an incident without unreasonable delay. The SEC changed the proposed wording "as soon as reasonably practicable" to this. | Without unreasonable delay after discovery | SEC release 33-11216 | | Form 8-K Item 1.05 | Disclose a cybersecurity incident determined to be material, describing the material aspects of its nature, scope and timing, and its impact or reasonably likely impact. | Within four business days of determining the incident was material | SEC release 33-11216 | | Delay for national security | A filing may be delayed if the United States Attorney General determines that immediate public filing would pose a substantial risk to national security or public safety. | As the Attorney General determines | SEC release 33-11216 | | Amendment | Amend a prior Item 1.05 Form 8-K to report information that was not determined or was unavailable at the first filing. The first filing must say which Item 1.05(a) information is not yet determined or is unavailable. | Within four business days after the information is determined or becomes available | SEC release 33-11216 | 10A. U.S. public companies: SEC Form 8-K Item 1.05 ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for healthcare](/templates/incident-response-plan-template-healthcare/) - [Incident response plan template for financial services](/templates/incident-response-plan-template-financial-services/) - [Incident response plan template for SaaS and technology companies](/templates/incident-response-plan-template-saas/) - [Incident response plan template for schools](/templates/incident-response-plan-template-school/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - SEC final rule 33-11216, Federal Register, 4 August 2023: https://www.federalregister.gov/documents/2023/08/04/2023-16194/cybersecurity-risk-management-strategy-governance-and-incident-disclosure (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-public-company/ --- # Incident response plan template for SaaS and technology companies Template, read 16 November 2026 **The short answer.** The incident response plan template for software and cloud providers adds the duties a provider owes its customers: GDPR processor notice without undue delay, HIPAA business associate notice within 60 days, and NIS2 notice to service recipients. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does an incident response plan for a SaaS company need? A software or cloud provider usually acts as a processor for its customers, so its plan must start the customers' clocks. GDPR Article 33(2) says a processor notifies the controller without undue delay after becoming aware of a personal data breach. HIPAA 164.410 says a business associate notifies the covered entity within 60 days at the latest. NIS2 Article 23(1) adds that essential and important entities notify the recipients of their services, where appropriate and without undue delay, of significant incidents likely to affect the service. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-saas.docx). PDF (76 KB): [download](/downloads/incident-response-saas.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. Software and cloud providers: duties to customers Use this addendum if your organization stores or processes customer data on their behalf. Your customers carry their own clocks, and your notice starts theirs. - Keep a current list of customers by data type and region so legal can see who must hear from you, and in what order. - Decide in advance who posts to the status page and what it may say, so that customers hear from you before they read about it elsewhere. - Add a sub-processor list to section 12 with each sub-processor's duty to tell you. - Keep logs long enough to answer customer questions about what was accessed. | Duty | What the rule says | Deadline | Source | | --- | --- | --- | --- | | GDPR processor | A processor notifies the controller of a personal data breach after becoming aware of it. | Without undue delay | GDPR Article 33(2) | | HIPAA business associate | A business associate that discovers a breach of unsecured protected health information notifies the covered entity. | Without unreasonable delay and no later than 60 calendar days after discovery | 45 CFR 164.410 | | NIS2 recipients of services | Essential and important entities notify, where appropriate and without undue delay, the recipients of their services of significant incidents likely to adversely affect the provision of those services. | Without undue delay | NIS2 Article 23(1) | | Contracts | Customer agreements often set shorter times and named contacts. Record each one in the contact sheet. | Per contract | Your contracts | 10A. Software and cloud providers: duties to customers ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for financial services](/templates/incident-response-plan-template-financial-services/) - [Incident response plan template for public companies](/templates/incident-response-plan-template-public-company/) - [Incident response plan template for schools](/templates/incident-response-plan-template-school/) - [Incident response plan template for federal agencies](/templates/incident-response-plan-template-federal-agency/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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.410, Notification by a business associate: https://www.ecfr.gov/current/title-45/section-164.410 (read 16 November 2026) - Directive (EU) 2022/2555 (NIS2), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-saas/ --- # Incident response plan template for schools Template, read 16 November 2026 **The short answer.** The school incident response plan template follows the U.S. Department of Education PTAC Data Breach Response Checklist of September 2012. FERPA itself has no specific breach notification requirement, but state laws and other federal laws may apply. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does an incident response plan for a school need? A school plan needs a written breach policy, a map of where student personal information lives (including backups and vendors), monitoring, recurring training, and a response sequence of validate, scope, notify data owners, decide on law enforcement and decide on notifying individuals. This is the structure of the PTAC checklist. PTAC states that FERPA does not itself contain specific breach notification requirements, that most states have breach notification laws, and that federal laws such as the Gramm-Leach-Bliley Act, the FTC Act and HITECH may apply. Always check with counsel. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-school.docx). PDF (76 KB): [download](/downloads/incident-response-school.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. Schools and education agencies: student data Use this addendum for a school, district, college or education agency. The U.S. Department of Education's Privacy Technical Assistance Center (PTAC) publishes a breach response checklist for these organizations. - Name the data owners (for example the student information system owner and each cloud vendor) in section 12 with the person to call. - Add the state student privacy and breach notification statutes that apply to your state in the section 10 table, after checking with counsel. - Write the parent and student notice in plain language and keep a translated version if your community needs one. | Point | What the source says | Source | | --- | --- | --- | | FERPA and notice | FERPA itself does not contain specific breach notification requirements. It protects the confidentiality of education records by requiring a record of each release of student data. | PTAC checklist, September 2012 | | State and other federal laws | Most states have breach notification laws. Federal laws that may apply include the Gramm-Leach-Bliley Act, the FTC Act, the HITECH Act and FERPA. Check each with counsel. | PTAC checklist, September 2012 | | Before a breach | Write a breach response policy; find where personally identifiable information lives, including backups; monitor for leakage; train staff on a recurring basis. | PTAC checklist, September 2012 | | Responding | Validate the breach; determine its scope and composition; notify data owners; decide whether to notify law enforcement; decide whether, when and how to notify affected individuals. | PTAC checklist, September 2012 | 10A. Schools and education agencies: student data ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for public companies](/templates/incident-response-plan-template-public-company/) - [Incident response plan template for SaaS and technology companies](/templates/incident-response-plan-template-saas/) - [Incident response plan template for federal agencies](/templates/incident-response-plan-template-federal-agency/) - [Incident response plan template for the UK](/templates/incident-response-plan-template-uk/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-school/ --- # Incident response plan template for federal agencies Template, read 16 November 2026 **The short answer.** The federal agency incident response plan template follows the CISA Cybersecurity Incident & Vulnerability Response Playbooks of November 2021, which require Federal Civilian Executive Branch agencies to report every cybersecurity incident to CISA. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does a federal incident response plan need? A federal plan needs a reporting step to CISA, a coordination lead, escalation rules for major incidents, and evidence sharing with law enforcement. CISA says FCEB agencies must promptly report all cybersecurity incidents, regardless of severity, and that every incident affecting an agency must be reported. The playbook follows the phases of NIST SP 800-61 Rev. 2, which NIST superseded with Rev. 3 in April 2025. CISA states that future iterations may be useful for organizations outside the FCEB. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-federal.docx). PDF (77 KB): [download](/downloads/incident-response-federal.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. U.S. federal civilian agencies: reporting to CISA Use this addendum for a Federal Civilian Executive Branch (FCEB) agency. CISA's playbook applies to these agencies; other organizations may use it as a model. - Add the agency's CISA liaison and the OMB contact to the contact sheet. - Use the playbook's Appendix B checklist as the working checklist during a major incident. - Add continuity-of-operations contacts to section 3 if the agency's COOP plan applies. | Duty | What the playbook says | Source | | --- | --- | --- | | Report every incident | FCEB agencies must promptly report all cybersecurity incidents, regardless of severity, to CISA. "Declaring" an incident means reporting it to CISA at cisa.gov/report and alerting agency IT leadership. | CISA playbook, November 2021 | | Major incidents | Report major incidents to CISA and to OMB at the address the playbook gives. CISA can help decide whether an incident should be declared a major incident. | CISA playbook, November 2021 | | Coordination lead | Document processes for designating a coordination lead (incident manager), escalation of major incidents, surge staffing, and evidence sharing with law enforcement. | CISA playbook, November 2021 | | Playbook basis | The playbook follows the phases of NIST SP 800-61 Rev. 2: preparation, detection and analysis, containment, eradication and recovery, and post-incident activities. NIST published Rev. 3 in April 2025. | CISA playbook; NIST | 10A. U.S. federal civilian agencies: reporting to CISA ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for SaaS and technology companies](/templates/incident-response-plan-template-saas/) - [Incident response plan template for schools](/templates/incident-response-plan-template-school/) - [Incident response plan template for the UK](/templates/incident-response-plan-template-uk/) - [Incident response checklist template](/templates/incident-response-checklist-template/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) - NIST SP 800-61 Rev. 3, publication page (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-federal-agency/ --- # Incident response plan template for the UK Template, read 16 November 2026 **The short answer.** The UK incident response plan template adds the ICO 72-hour breach report and the NCSC contact points to the general plan. The ICO says to report within 72 hours of becoming aware, where feasible, in phases if needed. Read on 16 November 2026. It is in full below, with free Word and PDF downloads. ## What does a UK incident response plan need? A UK plan needs a decision on whether a personal data breach is notifiable, a way to report to the ICO within 72 hours of becoming aware of it where feasible, and contacts at the NCSC. If notification takes longer than 72 hours, the ICO says you must give reasons for the delay. The ICO says Article 33(4) lets you provide information in phases and that you should still notify when you become aware. It also says the Data Use and Access Act changed PECR breach reports from 24 hours to 72 hours from 20 August 2025. ## The rules this template adds The table in section 10A of the template lists each rule, what it requires, its deadline and its source. Read the source before you rely on a summary. ## Download the template Free, no sign-up. Word (.docx, 9 KB): [download](/downloads/incident-response-uk.docx). PDF (76 KB): [download](/downloads/incident-response-uk.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 10A. United Kingdom: ICO and NCSC Use this addendum for an organization that processes personal data in the United Kingdom. - Add the ICO and NCSC to the contact sheet, with the NCSC number printed in the guide: 0300 123 2040. - Write down who decides whether a breach is notifiable and on what test, and record the time you became aware. - For the first report, say what happened, what data is involved and what you are doing, and add detail later; the ICO allows phased reports. | Duty | What the source says | Deadline | Source | | --- | --- | --- | --- | | Report to the ICO | Report a notifiable personal data breach to the Information Commissioner's Office. If you take longer than 72 hours you must give reasons for the delay. | Without undue delay and no later than 72 hours after becoming aware, where feasible | ICO guide | | Phased reporting | It is not always possible to investigate fully within 72 hours, so Article 33(4) lets you provide information in phases without undue further delay. The ICO says to tell it when you expect more detail. | Initial report within 72 hours, then as soon as possible | ICO guide | | Communications service providers | Providers report breaches under the Privacy and Electronic Communications Regulations on a separate form. The ICO says the Data Use and Access Act changed the PECR period from 24 hours to 72 hours on 20 August 2025. | 72 hours | ICO guide | | NCSC live attack | A business, charity or other organization suffering a live cyber attack can call the NCSC. It states the service is available 24 hours a day, 7 days a week. | Immediately | NCSC small business guide | 10A. United Kingdom: ICO and NCSC ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for schools](/templates/incident-response-plan-template-school/) - [Incident response plan template for federal agencies](/templates/incident-response-plan-template-federal-agency/) - [Incident response checklist template](/templates/incident-response-checklist-template/) - [Incident response plan template: Word and PDF downloads](/templates/incident-response-plan-template-word-pdf/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - ICO, Personal data breaches: a guide: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-uk/ --- # Incident response checklist template Template, read 16 November 2026 **The short answer.** The incident response checklist template covers the first hours of any incident and four forms: incident log, timeline, handover note and closing report. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026. CISA and SANS publish similar checklists. ## Is there an incident response checklist template? Yes. CISA's playbook includes Appendix B, an incident response checklist with step, procedure, action taken and date completed columns, and Appendix C, a preparation checklist. The SANS handbook ends with an Incident Handlers Checklist for preparation, identification, containment, eradication, recovery and lessons learned. This template takes the same idea in a shorter form: a first-hours checklist and four forms to copy into your records system. ## Download the template Free, no sign-up. Word (.docx, 3 KB): [download](/downloads/incident-response-forms.docx). PDF (49 KB): [download](/downloads/incident-response-forms.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### First-hours checklist Tick each item and write the time. Hand the page to the next shift with the log. | Step | Done | Time | By | | --- | --- | --- | --- | | Incident declared. Severity set. Log opened. | [ ] | | | | Incident lead, technical lead and communications lead called. | [ ] | | | | Out-of-band channel opened (phone bridge or secure group). | [ ] | | | | Affected systems, accounts and data listed. Unknowns listed. | [ ] | | | | Evidence preserved before any change: logs saved, images taken where needed. | [ ] | | | | Containment actions approved and recorded. | [ ] | | | | Legal and privacy lead told. Notice clocks started and times recorded. | [ ] | | | | Insurer and outside responders told, if the policy or plan requires it. | [ ] | | | | First message to staff approved by the communications lead. | [ ] | | | | Next update time set and announced. | [ ] | | | | Handover note written if the shift changes. | [ ] | | | First-hours checklist ### Form A: incident log One row per entry. Never edit a row; add a new row to correct it. | No. | Date and time (zone) | Recorded by | What was observed or done | System or account | Evidence id | Decision and approver | | --- | --- | --- | --- | --- | --- | --- | | 1 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | | 2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | | 3 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | Form A: incident log ### Form B: timeline Fill in as facts are confirmed. Mark estimates with "est.". | Event | Date and time (zone) | Source of the time | | --- | --- | --- | | First malicious activity | [ ] | [ ] | | Detected | [ ] | [ ] | | Reported | [ ] | [ ] | | Declared | [ ] | [ ] | | Contained | [ ] | [ ] | | Notice clock started (one row per rule) | [ ] | [ ] | | Notices sent (one row per recipient) | [ ] | [ ] | | Recovery started | [ ] | [ ] | | Recovery declared complete | [ ] | [ ] | | Review held | [ ] | [ ] | Form B: timeline ### Form C: handover note Write this at every change of shift, in under one page. - Current status and severity. - Actions open, with owners. - Decisions waiting, and who must make them. - People on shift and how to reach them. - Next update time and audience. - Where the log and evidence are. ### Form D: closing report outline The incident lead completes this before the review meeting. 1. Summary in five sentences. 2. Timeline (Form B). 3. Cause and how it was found. 4. Impact: systems, people, data, money, hours. 5. Notices sent, to whom and when. 6. What worked and what did not. 7. Actions: owner, due date, status. 8. Changes made to this plan. ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for federal agencies](/templates/incident-response-plan-template-federal-agency/) - [Incident response plan template for the UK](/templates/incident-response-plan-template-uk/) - [Incident response plan template: Word and PDF downloads](/templates/incident-response-plan-template-word-pdf/) - [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-checklist-template/ --- # Incident response plan template: Word and PDF downloads Guide, read 16 November 2026 **The short answer.** Every template on this site downloads as a Word .docx and as a PDF, with no sign-up. The files are generated from the same text as the pages, so the page, the Word file and the PDF always match. This page, read on 16 November 2026, lists the files with sizes and explains how to edit them. ## Can I download the incident response plan template as Word or PDF? Yes. Each template page has a Word .docx and a PDF, and the table below links all of them. The Word files use standard headings and tables, so any word processor opens them. The PDFs are print-ready on Letter paper. Fields in [square brackets] are for you to fill in. Delete the italic guidance as you go. | Template | Word | PDF | | --- | --- | --- | | [Incident response plan template](/) | [.docx, 8 KB](/downloads/incident-response-general.docx) | [PDF, 73 KB](/downloads/incident-response-general.pdf) | | [Incident response plan template, NIST CSF 2.0 layout](/templates/incident-response-plan-template-nist/) | [.docx, 9 KB](/downloads/incident-response-nist-layout.docx) | [PDF, 77 KB](/downloads/incident-response-nist-layout.pdf) | | [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) | [.docx, 3 KB](/downloads/incident-response-small-business.docx) | [PDF, 45 KB](/downloads/incident-response-small-business.pdf) | | [Incident response plan template: Health care](/templates/incident-response-plan-template-healthcare/) | [.docx, 9 KB](/downloads/incident-response-healthcare.docx) | [PDF, 78 KB](/downloads/incident-response-healthcare.pdf) | | [Incident response plan template: Financial services](/templates/incident-response-plan-template-financial-services/) | [.docx, 9 KB](/downloads/incident-response-financial.docx) | [PDF, 79 KB](/downloads/incident-response-financial.pdf) | | [Incident response plan template: Public company](/templates/incident-response-plan-template-public-company/) | [.docx, 9 KB](/downloads/incident-response-public-company.docx) | [PDF, 78 KB](/downloads/incident-response-public-company.pdf) | | [Incident response plan template: Software and cloud provider](/templates/incident-response-plan-template-saas/) | [.docx, 9 KB](/downloads/incident-response-saas.docx) | [PDF, 76 KB](/downloads/incident-response-saas.pdf) | | [Incident response plan template: School or education agency](/templates/incident-response-plan-template-school/) | [.docx, 9 KB](/downloads/incident-response-school.docx) | [PDF, 76 KB](/downloads/incident-response-school.pdf) | | [Incident response plan template: Federal agency](/templates/incident-response-plan-template-federal-agency/) | [.docx, 9 KB](/downloads/incident-response-federal.docx) | [PDF, 77 KB](/downloads/incident-response-federal.pdf) | | [Incident response plan template: United Kingdom](/templates/incident-response-plan-template-uk/) | [.docx, 9 KB](/downloads/incident-response-uk.docx) | [PDF, 76 KB](/downloads/incident-response-uk.pdf) | | [Phishing incident playbook](/playbooks/incident-response-playbook-phishing/) | [.docx, 3 KB](/downloads/incident-response-pb-phishing.docx) | [PDF, 48 KB](/downloads/incident-response-pb-phishing.pdf) | | [Business email compromise playbook](/playbooks/business-email-compromise-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-bec.docx) | [PDF, 47 KB](/downloads/incident-response-pb-bec.pdf) | | [Malware incident playbook](/playbooks/malware-incident-response-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-malware.docx) | [PDF, 46 KB](/downloads/incident-response-pb-malware.pdf) | | [Insider incident playbook](/playbooks/insider-threat-incident-response-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-insider.docx) | [PDF, 46 KB](/downloads/incident-response-pb-insider.pdf) | | [Lost or stolen device playbook](/playbooks/lost-or-stolen-device-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-lost-device.docx) | [PDF, 46 KB](/downloads/incident-response-pb-lost-device.pdf) | | [Cloud account compromise playbook](/playbooks/cloud-account-compromise-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-cloud-account.docx) | [PDF, 46 KB](/downloads/incident-response-pb-cloud-account.pdf) | | [DDoS attack playbook](/playbooks/incident-response-playbook-for-ddos-attack/) | [.docx, 3 KB](/downloads/incident-response-pb-ddos.docx) | [PDF, 46 KB](/downloads/incident-response-pb-ddos.pdf) | | [Third-party and supplier incident playbook](/playbooks/third-party-incident-response-playbook/) | [.docx, 3 KB](/downloads/incident-response-pb-third-party.docx) | [PDF, 46 KB](/downloads/incident-response-pb-third-party.pdf) | | [Incident response playbook template](/playbooks/incident-response-playbook-template/) | [.docx, 3 KB](/downloads/incident-response-playbook-template.docx) | [PDF, 40 KB](/downloads/incident-response-playbook-template.pdf) | | [Data breach response plan template](/data-breach/data-breach-response-plan-template/) | [.docx, 4 KB](/downloads/incident-response-data-breach.docx) | [PDF, 52 KB](/downloads/incident-response-data-breach.pdf) | | [Incident response checklist and forms](/templates/incident-response-checklist-template/) | [.docx, 3 KB](/downloads/incident-response-forms.docx) | [PDF, 49 KB](/downloads/incident-response-forms.pdf) | Can I download the incident response plan template as Word or PDF? ## How are the files made? A small script writes each Word file as a minimal Office Open XML package using Python's zipfile module, with headings, paragraphs and tables, then checks that every XML part is well formed. A second script prints the same text as a print-friendly page to PDF with Playwright. Because both files come from one text source, a correction made on a page reaches the downloads on the next build. The [method page](/templates/method/) records the details. ## Can I reuse the templates? Yes. The text is released under CC BY 4.0: copy it, change it and use it inside your organization, and link to the page when you publish it. The legal rules quoted in the company-type templates are summaries with sources; confirm them with counsel before relying on them. Start from the [general template](/) or choose a [company type](/templates/). ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response plan template for the UK](/templates/incident-response-plan-template-uk/) - [Incident response checklist template](/templates/incident-response-checklist-template/) - [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) - [Incident response plan template based on NIST](/templates/incident-response-plan-template-nist/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/incident-response-plan-template-word-pdf/ --- # Data breach response plan: what it is and how to write one Guide, read 16 November 2026 **The short answer.** A data breach response plan sets out how an organization finds, contains, assesses, reports and learns from an exposure of personal data. It differs from a general incident plan by adding the notification decision. This page, read on 16 November 2026, gives the seven parts and links to a free template. ## What is a data breach response plan? A data breach response plan is the part of incident response that deals with personal data. The U.S. Department of Education PTAC says establishing a clear plan, with defined roles and responsibilities, promotes better coordination and shortens response time, and that prompt response limits further data loss and harm to affected people. It sits beside the general incident response plan and shares its roles, severity levels and contact sheet. ## What are the seven parts of a data breach response plan? The template has seven parts: purpose and breach team; discover, report and contain; assess the breach; decide who must be told; write the notice; support affected people; document and review. The decision step is the one the general plan lacks. 1. Purpose, scope and breach team. 2. Discover, report and contain. 3. Assess the breach: data, people, cause, protection, harm. 4. Decide who must be told, and by when. 5. Write the notice with the required content. 6. Support affected people. 7. Document and review. ## Which clocks start a breach plan? The clocks differ by rule, so the plan lists each. GDPR Article 33 gives 72 hours to the authority, where feasible. HIPAA 164.404 gives 60 calendar days to individuals. The FTC Safeguards Rule gives 30 days to the FTC for events involving 500 or more consumers. Read the [GDPR page](/data-breach/data-breach-response-plan-gdpr/) and the [list of contents](/data-breach/what-should-a-data-breach-response-plan-include/), then download the [template](/data-breach/data-breach-response-plan-template/). ## All data breach pages - [Data breach response plan template](/data-breach/data-breach-response-plan-template/) - [Data breach response plan under GDPR](/data-breach/data-breach-response-plan-gdpr/) - [What should a data breach response plan include?](/data-breach/what-should-a-data-breach-response-plan-include/) ## Related pages - [Free incident response plan template](/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Incident response plan templates: the full set](/templates/) - [Incident response plan: what it contains and how to build one](/plans/) - [The standards map](/standards-map/) ## Sources - 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) - 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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/ --- # Data breach response plan template Template, read 16 November 2026 **The short answer.** The data breach response plan template has seven parts, from the breach team to the review, and a table for deciding who must be told. It is in full below and downloads as Word and PDF without sign-up. Read on 16 November 2026; the notice content follows GDPR Article 33(3) and 45 CFR 164.404(c). ## How do you use the data breach response plan template? Fill the bracketed fields, then have counsel confirm the notice table in part 4 for the laws that apply to you. Keep the plan next to the general incident response plan, because the two share roles and contacts. In an incident, the incident lead opens the log, the privacy lead completes part 4 within the time set, and the communications lead writes the notice from part 5. ## Download the template Free, no sign-up. Word (.docx, 4 KB): [download](/downloads/incident-response-data-breach.docx). PDF (52 KB): [download](/downloads/incident-response-data-breach.pdf). Both files carry the same text as this page, edition 16 November 2026. ## The template in full ### 1. Purpose, scope and breach team This plan applies when personal or regulated data may have been accessed, disclosed, lost or altered without authority, at [Organization name] or at a supplier that holds our data. - Breach team: incident lead [name]; privacy lead [name]; legal counsel [name]; communications lead [name]; technical lead [name]; executive sponsor [name]; each with a named deputy. - The team has authority to [take systems offline, suspend accounts, engage outside experts] without further approval. ### 2. Discover, report and contain Anyone who suspects a breach reports it at once. The incident lead records the time of discovery. 1. Record the date and time the breach was first known, and who knew. 2. Stop the exposure: revoke access, take down the page or share, recover the device or message where possible. 3. Preserve logs and evidence. Do not wipe systems yet. 4. Open the log and the decision record. ### 3. Assess the breach Answer these questions, in writing, as soon as the facts allow. Update the answers as the investigation develops. - What data: types of data and, for each, the number of people and records. - Whose data: customers, employees, patients, students, children; which countries and states. - How: cause and whether the breach is still happening. - Was the data protected, for example by strong encryption, so that it is unintelligible to unauthorized people? - Who has it: an unknown actor, a known recipient, a supplier, a misdirected email. - What harm could follow: fraud, identity theft, physical or reputational harm, discrimination. ### 4. Decide who must be told The privacy lead and counsel complete this table within [24 hours] of discovery and revisit it daily. | Recipient | Test for notifying | Deadline | Decision, time and owner | | --- | --- | --- | --- | | Supervisory authority or regulator | [rule and test from section 10 of the plan] | [deadline] | | | Affected individuals | [rule and test] | [deadline] | | | Customers whose data we process | [contract clause] | [deadline] | | | Insurer | [policy clause] | [deadline] | | | Law enforcement | [when advised by counsel] | n/a | | | Payment brands, banks, other contractual parties | [contract clause] | [deadline] | | 4. Decide who must be told Examples of tests, each from the source named on this site: GDPR Article 33 (72 hours to the authority unless the breach is unlikely to result in a risk), Article 34 (communicate to individuals when likely to result in a high risk), HIPAA 164.404 (60 days to individuals), FTC Safeguards Rule 314.4(j) (30 days to the FTC for 500 or more consumers). ### 5. Write the notice Use plain language. Include the same minimum content for every audience, then add what the audience needs. - What happened, with dates, and when it was discovered. - The categories and approximate number of people and records involved. - The likely consequences. - What we have done and are doing, including steps to limit harm. - What recipients should do to protect themselves. - How to ask questions: name or role, phone, email, website or postal address. GDPR Article 33(3) lists the elements on what happened, the categories and numbers, the likely consequences, the measures taken and the contact point. The element on what recipients should do to protect themselves comes from 45 CFR 164.404(c)(1)(C); GDPR reaches it only through the mitigation measures in Article 33(3)(d) and Article 34(2). ### 6. Support affected people Decide what help to offer and who delivers it. - Dedicated phone line or mailbox: [details], staffed [hours]. - Offers such as credit monitoring or identity protection where the data supports a need: [offer, provider, duration]. - A frequently asked questions page, updated daily until closure. ### 7. Document and review Document every breach, even one that is not reported to anyone. - Record the facts, the effects and the remedial action, in a form that lets a regulator check compliance (GDPR Article 33(5)). - Hold a review within [10 business days] of closure: cause, controls that failed, what to change, owners and dates. - Update the plan, the notice templates and the training. ## Related pages - [Data breach response plan: what it is and how to write one](/data-breach/) - [Free incident response plan template](/) - [Data breach response plan under GDPR](/data-breach/data-breach-response-plan-gdpr/) - [What should a data breach response plan include?](/data-breach/what-should-a-data-breach-response-plan-include/) - [Incident response plan templates: the full set](/templates/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) - 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) - 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) - ICO, Personal data breaches: a guide: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/data-breach-response-plan-template/ --- # Data breach response plan under GDPR Guide, read 16 November 2026 **The short answer.** Under GDPR Article 33 a controller must notify the supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk. This page, read on 16 November 2026, lists what a plan must do to meet it. ## How does GDPR affect a data breach response plan? GDPR sets a 72-hour clock, a content list, a phasing rule, a documentation rule and a separate duty to tell individuals. Article 33(1) requires the controller to notify the competent authority without undue delay and, where feasible, not later than 72 hours after becoming aware, with reasons if later. Article 33(3) lists the minimum content, Article 33(4) allows phased information, and Article 33(5) requires documenting every breach. | Article | Duty | Plan section | | --- | --- | --- | | 33(1) | Notify the authority within 72 hours where feasible, unless unlikely to risk rights and freedoms | Part 4 | | 33(2) | Processor notifies controller without undue delay | Part 4; supplier contacts | | 33(3) | Notice describes the breach, contact point, likely consequences, measures taken | Part 5 | | 33(4) | Information may be provided in phases | Part 5 | | 33(5) | Document every breach: facts, effects, remedial action | Part 7 | | 34(1) | Tell individuals without undue delay when high risk | Parts 4 and 5 | | 34(3) | No duty if data was protected, risk no longer likely, or disproportionate effort | Part 3 | How does GDPR affect a data breach response plan? ## When must individuals be told under GDPR? Article 34 requires the controller to communicate the breach to the data subject without undue delay when it is likely to result in a high risk to their rights and freedoms, in clear and plain language. It need not do so if the data was made unintelligible, for example by encryption, if later measures mean the high risk is no longer likely, or if it would involve disproportionate effort, in which case a public communication is used. ## What does the UK regulator add? The ICO guide says the UK GDPR requires reporting within 72 hours of becoming aware where feasible and that prioritizing and expediting the investigation is expected. See the [UK template](/templates/incident-response-plan-template-uk/). For NIS2 entities, Article 23 sets a 24-hour early warning, a 72-hour incident notification and a final report within one month for significant incidents. The [SaaS template](/templates/incident-response-plan-template-saas/) shows how provider duties fit. ## Related pages - [Data breach response plan: what it is and how to write one](/data-breach/) - [Free incident response plan template](/) - [What should a data breach response plan include?](/data-breach/what-should-a-data-breach-response-plan-include/) - [Data breach response plan template](/data-breach/data-breach-response-plan-template/) - [Incident response plan templates: the full set](/templates/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - Regulation (EU) 2016/679 (GDPR), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679 (read 16 November 2026) - ICO, Personal data breaches: a guide: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (read 16 November 2026) - Directive (EU) 2022/2555 (NIS2), EUR-Lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/data-breach-response-plan-gdpr/ --- # What should a data breach response plan include? Guide, read 16 November 2026 **The short answer.** A data breach response plan should include a written policy, a map of where personal data lives, monitoring, training, a response sequence from validation to notification, and notice content that meets the law. This page, read on 16 November 2026, gives the checklist drawn from PTAC, HIPAA and GDPR. ## What should a data breach response plan include? It should include the building blocks the PTAC checklist lists for use before a breach, and the response steps it lists during one. Before: a written breach response policy; a review of where personally identifiable information is stored, including backups and archives; continuous monitoring for leakage; and recurring training. During: validate the breach, determine its scope and composition, notify the data owners, decide whether to notify law enforcement, and decide whether and how to notify affected individuals. PTAC says the checklist is not linear and that some activities happen at once. 1. Written breach policy and named breach team with a deputy. 2. Data map: what, where, who has access. 3. Monitoring and loss detection. 4. Recurring staff training. 5. Validate and scope the breach. 6. Notify data owners. 7. Decide on law enforcement. 8. Decide on, write and send notices. 9. Document and review. ## What must the notice itself contain? The content lists in the sources agree on the core. HIPAA 164.404(c) requires a brief description of what happened with dates, the types of information involved, steps individuals should take, what the entity is doing, and contact procedures including a toll-free number, email address, website or postal address, in plain language. GDPR Article 33(3) requires the nature of the breach with categories and approximate numbers of people and records, a contact point, likely consequences and the measures taken or proposed. | Element | HIPAA 164.404(c) | GDPR 33(3) | | --- | --- | --- | | What happened | Yes, with dates | Nature, categories and numbers | | Data involved | Types of information | Categories of records | | Advice to people | Steps to protect themselves | Via Article 34 for individuals | | Our response | Investigation, mitigation, prevention | Measures taken or proposed | | Contact | Toll-free number, email, website or postal address | Name and contact of DPO or contact point | | Consequences | Not listed | Likely consequences | What must the notice itself contain? ## Does a breach plan have to be separate? Not necessarily. Many organizations keep one incident response plan with a breach section. Keeping a [separate template](/data-breach/data-breach-response-plan-template/) is useful when a privacy team owns the notification decision. See the [overview](/data-breach/) for the seven parts. ## Related pages - [Data breach response plan: what it is and how to write one](/data-breach/) - [Free incident response plan template](/) - [Data breach response plan template](/data-breach/data-breach-response-plan-template/) - [Data breach response plan under GDPR](/data-breach/data-breach-response-plan-gdpr/) - [Incident response plan templates: the full set](/templates/) - [Incident response plan: what it contains and how to build one](/plans/) ## Sources - 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) - eCFR, 45 CFR 164.404, Notification to individuals: https://www.ecfr.gov/current/title-45/section-164.404 (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) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/data-breach/what-should-a-data-breach-response-plan-include/ --- # Incident response plan template: free, in full, with Word and PDF Template, read 16 November 2026 **The short answer.** The free incident response plan template below has fifteen sections, from roles and severity levels to legal notices and forms. The full text is on this page and downloads as Word and PDF with no sign-up. Variants for company types and incident types follow. Read and checked against NIST, CISA, SANS and regulator sources on 16 November 2026. ## Where can I find a free incident response plan template? You are on it. The general incident response plan template below is free to copy and adapt, and it is in full on this page. Fields in square brackets are for you to fill in. It follows the sections that NIST SP 800-61 Rev. 3 (April 2025) and CISA's playbook describe, mapped on the [standards map](/standards-map/). Download it as [Word](/downloads/incident-response-general.docx) or [PDF](/downloads/incident-response-general.pdf). ## Which version of the template fits your organization? Choose the general template for most organizations. Choose a company-type version if a specific rule adds notice duties or plan contents, and an incident-type playbook for a scenario your team is likely to face. ### By company type - [Incident response plan template, NIST CSF 2.0 layout](/templates/incident-response-plan-template-nist/): Organizations that already use the NIST Cybersecurity Framework - [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/): Small and medium-sized organizations with little or no security staff - [Incident response plan template: Health care](/templates/incident-response-plan-template-healthcare/): HIPAA covered entities and business associates - [Incident response plan template: Financial services](/templates/incident-response-plan-template-financial-services/): Financial institutions under the FTC Safeguards Rule; covered entities under 23 NYCRR 500 - [Incident response plan template: Public company](/templates/incident-response-plan-template-public-company/): U.S. companies that file Exchange Act reports - [Incident response plan template: Software and cloud provider](/templates/incident-response-plan-template-saas/): Providers that process customer data - [Incident response plan template: School or education agency](/templates/incident-response-plan-template-school/): Schools, districts, colleges and education agencies - [Incident response plan template: Federal agency](/templates/incident-response-plan-template-federal-agency/): Federal Civilian Executive Branch agencies - [Incident response plan template: United Kingdom](/templates/incident-response-plan-template-uk/): Organizations processing personal data in the UK ### By incident type - [Phishing incident playbook](/playbooks/incident-response-playbook-phishing/) - [Business email compromise playbook](/playbooks/business-email-compromise-playbook/) - [Malware incident playbook](/playbooks/malware-incident-response-playbook/) - [Insider incident playbook](/playbooks/insider-threat-incident-response-playbook/) - [Lost or stolen device playbook](/playbooks/lost-or-stolen-device-playbook/) - [Cloud account compromise playbook](/playbooks/cloud-account-compromise-playbook/) - [DDoS attack playbook](/playbooks/incident-response-playbook-for-ddos-attack/) - [Third-party and supplier incident playbook](/playbooks/third-party-incident-response-playbook/) ### Other - [Data breach response plan template](/data-breach/data-breach-response-plan-template/) - [Incident response steps](/steps/) - [Incident response playbook library](/playbooks/) - [The template set, all files](/templates/) - [Firms that offer incident response planning](/services/) ## What is in the plan? Fifteen sections: purpose and authority; roles; contacts; severity; declaring an incident; triage; containment; eradication and recovery; communications; legal notices; evidence; third parties; review; testing and upkeep; forms. These templates do not include a ransomware-specific plan; CISA's [#StopRansomware Guide](https://www.cisa.gov/stopransomware/ransomware-guide) is the government reference. ## The template in full ### 1. Purpose, scope and authority This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it. - Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan]. - Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current. - Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval]. - Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5. - Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval. ### 2. Roles and responsibilities Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column. | Role | Name | Deputy | What this role decides | | --- | --- | --- | --- | | Executive sponsor | [name] | [name] | Funds the response. Approves shutting down or rebuilding critical services. | | Incident lead | [name] | [name] | Declares and closes the incident. Sets priorities. Runs the response meetings. | | Technical lead | [name] | [name] | Chooses containment and recovery actions. Directs system and network administrators. | | Communications lead | [name] | [name] | Approves every internal and external message. Is the only spokesperson. | | Legal and privacy lead | [name] | [name] | Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement. | | Human resources | [name] | [name] | Handles any case where an employee may be involved. | | Facilities and physical security | [name] | [name] | Gives responders physical access to sites and devices. | | System and data owners | [names] | [names] | Advise on recovery priority for their systems. Receive status updates. | | Scribe | [name] | [name] | Keeps the incident log in appendix A. | 2. Roles and responsibilities Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners. ### 3. Contact and escalation sheet Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down. | Who | Name or organization | Phone (24 hours) | Backup contact | Call when | | --- | --- | --- | --- | --- | | Incident lead | [name] | [number] | [number] | Any suspected incident | | Executive sponsor | [name] | [number] | [number] | Severity 3 or 4, or any legal duty to notify | | Legal counsel | [firm or person] | [number] | [number] | Any exposure of personal data, or any contact with a regulator | | Cyber insurer hotline | [insurer] | [number] | [policy number] | Before hiring outside responders, if the policy requires it | | Incident response firm | [firm] | [number] | [retainer reference] | Severity 3 or 4, or when the team cannot scope the incident | | Internet and cloud providers | [providers] | [numbers] | [account ids] | Attack on availability, or compromise of a cloud account | | Law enforcement | [agency and office] | [number] | | After legal counsel agrees, or when funds were sent | | Regulators | [agency per section 10] | [number or portal] | | As section 10 directs | 3. Contact and escalation sheet ### 4. Severity levels Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks. | Level | Criteria | Examples to adapt | Who is called | First response target | | --- | --- | --- | --- | --- | | 1 Low | One user or device. No sensitive data exposed. No service affected. | A blocked phishing email that no one opened. | Incident lead | [hours] | | 2 Medium | More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data. | One account compromised and reset before any data was accessed. | Incident lead, technical lead | [hours] | | 3 High | A critical service is down or degraded, or sensitive data may have been exposed. | Unauthorized access to a database holding customer records. | All roles in section 2, legal counsel | [minutes] | | 4 Critical | Wide loss of service, confirmed exposure of regulated data, or a threat to safety. | A compromised administrator account with access across the network. | All roles, executive sponsor, outside responders | [minutes] | 4. Severity levels Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes. ### 5. Detecting, reporting and declaring an incident Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident. - How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished. - Who receives reports: [role or team]. They log the report in appendix A within [15 minutes]. - Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria. - Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone. - On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10. ### 6. Triage and analysis Work through these steps in order, and record each one in the log. Several can run at the same time. 1. Validate: confirm the report is real and not authorized activity such as an administrator running remote tools. 2. Scope: list the affected users, devices, accounts, services and data. Note what is not yet known. 3. Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier]. 4. Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted. 5. Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image. 6. Re-rate the severity and update the people called. ### 7. Containment The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when. | Action | Who may approve | Business impact to weigh first | Logged where | | --- | --- | --- | --- | | Isolate a device from the network | [role] | [effect on users and services] | Appendix A | | Disable or reset an account | [role] | [effect on the person and linked services] | Appendix A | | Block an address, domain or file | [role] | [effect on legitimate traffic] | Appendix A | | Take a service offline | [role] | [customers and contracts affected] | Appendix A | | Rotate keys and service account secrets | [role] | [systems that will fail until updated] | Appendix A | 7. Containment Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it. ### 8. Eradication and recovery Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass. 1. Confirm containment: no new signs of attacker activity for [period]. 2. Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt. 3. Verify backups before restoring from them, and restore to clean systems only. 4. Test restored systems, then watch them closely for [period] for signs of re-entry. 5. Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]. ### 9. Communications One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing. | Audience | Owner | Channel | Approved by | Timing | | --- | --- | --- | --- | --- | | Employees | [role] | [channel] | Communications lead | [when] | | Customers and partners | [role] | [channel] | Communications lead, legal | [when] | | Regulators and law enforcement | Legal and privacy lead | [portal or phone] | Legal and privacy lead | As section 10 directs | | Insurer | [role] | [hotline] | Executive sponsor | [when] | | Media | Communications lead | Holding statement | Executive sponsor, legal | Only if asked or required | | Executives and board | Incident lead | [channel] | Incident lead | [interval] | 9. Communications Prepare a holding statement now: "We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions." ### 10. Legal, regulatory, contractual and insurance notices List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started. | Rule, contract or policy | Applies when | Deadline and to whom | Owner | Source | | --- | --- | --- | --- | --- | | [Name the law, for example a state breach notification law] | [trigger] | [deadline] to [authority or individuals] | [role] | [link] | | [Customer contract clause] | [trigger] | [deadline] to [customer] | [role] | [contract reference] | | [Cyber insurance policy] | [trigger] | [deadline] to [insurer] | [role] | [policy number] | | [Other] | [trigger] | [deadline] | [role] | [link] | 10. Legal, regulatory, contractual and insurance notices The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source. ### 11. Evidence handling and documentation Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action. - Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored. - Store logs, images and notes in a location only responders can reach. - For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since. - Do not edit entries after the fact. Add a correction as a new entry. ### 12. Third parties and suppliers List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises. | Third party | Service | Incident contact | Their duty to tell us | Our duty to tell them | | --- | --- | --- | --- | --- | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | | [provider] | [service] | [name and number] | [contract clause and time] | [when] | 12. Third parties and suppliers Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers. ### 13. Post-incident review Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame. - Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get. - Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date. - Update this plan, the contact sheet and the detections within [30 days]. - Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent. ### 14. Testing, training and keeping the plan current A plan that has not been practiced is a draft. - Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings. - Test restoring critical systems from backups at least once every [12 months]. - Training: every responder is trained for their role. All staff learn how to report an incident. - Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident. - Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty. ### Appendices: forms Copy these forms into your records system. Appendix A is opened on declaration and closed on review. | Appendix | Form | Fields | | --- | --- | --- | | A | Incident log | Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver | | B | Timeline | Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed | | C | Handover note | Current status; open actions; next decisions; people on shift; next update time; where the log is | | D | Closing report | Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates | Appendices: forms ## How is the plan builder data organized? The builder data pairs a company type with an incident type and lists the plan sections to include, in order. It is published as [plan-builder.json](/data/plan-builder.json) so that a builder tool can assemble a plan from the same section text used on these pages. ## Related pages - [Incident response plan guide](/plans/) - [Incident response steps](/steps/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Site method](/method/) ## 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) - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (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/ --- # Incident response plan templates: the full set Template set, read 16 November 2026 **The short answer.** The template set has 21 documents: a general plan, plans for health care, financial services, public companies, software providers, schools, federal agencies and the UK, a small business plan, eight playbooks, a data breach plan and forms. Each downloads as Word and PDF, free. Edition 16 November 2026. ## Which incident response plan templates are free? All of them. The table lists every template in the set with who it is for, the rule or guidance it follows and both downloads. There is no sign-up. The set is released under CC BY 4.0. | Template | For | Follows | Files | | --- | --- | --- | --- | | [Incident response plan template](/) | Any organization with an IT or security function, or one that outsources it | None required: built on the sections NIST SP 800-61 Rev. 3 and the CISA playbook describe | [.docx](/downloads/incident-response-general.docx), [PDF](/downloads/incident-response-general.pdf) | | [Incident response plan template, NIST CSF 2.0 layout](/templates/incident-response-plan-template-nist/) | Organizations that already use the NIST Cybersecurity Framework | NIST SP 800-61 Rev. 3 Community Profile | [.docx](/downloads/incident-response-nist-layout.docx), [PDF](/downloads/incident-response-nist-layout.pdf) | | [Incident response plan template for small business](/templates/incident-response-plan-template-for-small-business/) | Small and medium-sized organizations with little or no security staff | NCSC Small Business Guide: Response & Recovery (five steps) | [.docx](/downloads/incident-response-small-business.docx), [PDF](/downloads/incident-response-small-business.pdf) | | [Incident response plan template: Health care](/templates/incident-response-plan-template-healthcare/) | HIPAA covered entities and business associates | HIPAA Breach Notification Rule, 45 CFR 164.400 to 164.414 | [.docx](/downloads/incident-response-healthcare.docx), [PDF](/downloads/incident-response-healthcare.pdf) | | [Incident response plan template: Financial services](/templates/incident-response-plan-template-financial-services/) | Financial institutions under the FTC Safeguards Rule; covered entities under 23 NYCRR 500 | FTC Safeguards Rule 16 CFR 314.4(h) and (j); 23 NYCRR 500.16 and 500.17 | [.docx](/downloads/incident-response-financial.docx), [PDF](/downloads/incident-response-financial.pdf) | | [Incident response plan template: Public company](/templates/incident-response-plan-template-public-company/) | U.S. companies that file Exchange Act reports | SEC Form 8-K Item 1.05 | [.docx](/downloads/incident-response-public-company.docx), [PDF](/downloads/incident-response-public-company.pdf) | | [Incident response plan template: Software and cloud provider](/templates/incident-response-plan-template-saas/) | Providers that process customer data | GDPR Article 33(2); 45 CFR 164.410; NIS2 Article 23 | [.docx](/downloads/incident-response-saas.docx), [PDF](/downloads/incident-response-saas.pdf) | | [Incident response plan template: School or education agency](/templates/incident-response-plan-template-school/) | Schools, districts, colleges and education agencies | FERPA and the PTAC checklist; state breach laws | [.docx](/downloads/incident-response-school.docx), [PDF](/downloads/incident-response-school.pdf) | | [Incident response plan template: Federal agency](/templates/incident-response-plan-template-federal-agency/) | Federal Civilian Executive Branch agencies | CISA Cybersecurity Incident & Vulnerability Response Playbooks | [.docx](/downloads/incident-response-federal.docx), [PDF](/downloads/incident-response-federal.pdf) | | [Incident response plan template: United Kingdom](/templates/incident-response-plan-template-uk/) | Organizations processing personal data in the UK | UK GDPR Article 33 as explained by the ICO; NCSC guidance | [.docx](/downloads/incident-response-uk.docx), [PDF](/downloads/incident-response-uk.pdf) | | [Phishing incident playbook](/playbooks/incident-response-playbook-phishing/) | Staff report a suspicious message, or a user clicked a link or entered credentials | Microsoft publishes a five-stage workflow for phishing investigations; this playbook follows its stages in plain terms. | [.docx](/downloads/incident-response-pb-phishing.docx), [PDF](/downloads/incident-response-pb-phishing.pdf) | | [Business email compromise playbook](/playbooks/business-email-compromise-playbook/) | A payment request or bank detail change looks fraudulent, or an email account may be taken over | The FBI IC3 describes business email compromise (BEC) as a scam that targets businesses and individuals who perform transfer-of-funds requests, often through a compromised email account. | [.docx](/downloads/incident-response-pb-bec.docx), [PDF](/downloads/incident-response-pb-bec.pdf) | | [Malware incident playbook](/playbooks/malware-incident-response-playbook/) | Endpoint protection or a user reports malicious software on one or more devices | The NCSC defines malware as malicious software that can lock devices, steal, delete or encrypt data, take control of devices and obtain credentials. | [.docx](/downloads/incident-response-pb-malware.docx), [PDF](/downloads/incident-response-pb-malware.pdf) | | [Insider incident playbook](/playbooks/insider-threat-incident-response-playbook/) | A trusted person is suspected of misusing access, on purpose or by mistake | CISA defines an insider as any person who has or had authorized access to or knowledge of an organization's resources, and insider threat as the potential for that person to use the access to harm the organization. | [.docx](/downloads/incident-response-pb-insider.docx), [PDF](/downloads/incident-response-pb-insider.pdf) | | [Lost or stolen device playbook](/playbooks/lost-or-stolen-device-playbook/) | A laptop, phone, drive or paper record holding business data is lost or stolen | The U.S. Department of Education PTAC lists lost, stolen or temporarily misplaced equipment, such as laptops, mobile phones and portable thumb drives, among the forms a data breach can take. | [.docx](/downloads/incident-response-pb-lost-device.docx), [PDF](/downloads/incident-response-pb-lost-device.pdf) | | [Cloud account compromise playbook](/playbooks/cloud-account-compromise-playbook/) | A cloud user, administrator or service account is used by someone other than its owner | Microsoft publishes separate investigation playbooks for password spray, app consent grants and token theft, which are the common routes to a cloud account compromise. | [.docx](/downloads/incident-response-pb-cloud-account.docx), [PDF](/downloads/incident-response-pb-cloud-account.pdf) | | [DDoS attack playbook](/playbooks/incident-response-playbook-for-ddos-attack/) | A website, application or network service is slow or down from a flood of traffic | CISA, the FBI and MS-ISAC published a guide on 21 March 2024 that sorts DoS and DDoS techniques into three types: volumetric, protocol and application. | [.docx](/downloads/incident-response-pb-ddos.docx), [PDF](/downloads/incident-response-pb-ddos.pdf) | | [Third-party and supplier incident playbook](/playbooks/third-party-incident-response-playbook/) | A supplier reports a compromise, or its product, update or hold on your data is at risk | NIST SP 800-61 Rev. 3 includes the CSF 2.0 outcome GV.SC-08: relevant suppliers and other third parties are included in incident planning, response, and recovery activities. | [.docx](/downloads/incident-response-pb-third-party.docx), [PDF](/downloads/incident-response-pb-third-party.pdf) | | [Incident response playbook template](/playbooks/incident-response-playbook-template/) | Teams writing their own playbooks | Structure after Microsoft's playbooks: prerequisites, workflow, checklist, investigation steps | [.docx](/downloads/incident-response-playbook-template.docx), [PDF](/downloads/incident-response-playbook-template.pdf) | | [Data breach response plan template](/data-breach/data-breach-response-plan-template/) | Any organization that holds personal data | GDPR Articles 33 and 34; 45 CFR 164.404; 16 CFR 314.4(j) | [.docx](/downloads/incident-response-data-breach.docx), [PDF](/downloads/incident-response-data-breach.pdf) | | [Incident response checklist and forms](/templates/incident-response-checklist-template/) | Responders during the first hours of any incident | CISA playbook Appendix B (response checklist) as a model | [.docx](/downloads/incident-response-forms.docx), [PDF](/downloads/incident-response-forms.pdf) | The template set ## How do I pick one? Start with the [general template](/). Add the company-type addendum if one of its rules applies to you. Add playbooks for the incidents you are most likely to see. The [word and PDF page](/templates/incident-response-plan-template-word-pdf/) explains the files. **Cite this.** Incident Response Plan Templates, "Incident Response Plan Template Set", edition 16 November 2026, https://incidentresponseplantemplates.com/templates/. Data: [CSV](/datasets/incident-response-template-set.csv) and [JSON](/datasets/incident-response-template-set.json). ## Related - [How the template set was made](/templates/method/) - [The standards map](/standards-map/) - [Datasets](/datasets/) - [Checklist and forms](/templates/incident-response-checklist-template/) - [Playbook library](/playbooks/) ## Related pages - [Free incident response plan template](/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) - [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) - 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) - NCSC, Small Business Guide: Response & Recovery: https://www.ncsc.gov.uk/collection/small-business-guidance--response-and-recovery (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) - eCFR, 45 CFR 164.404, Notification to individuals: https://www.ecfr.gov/current/title-45/section-164.404 (read 16 November 2026) - SEC final rule 33-11216, Federal Register, 4 August 2023: https://www.federalregister.gov/documents/2023/08/04/2023-16194/cybersecurity-risk-management-strategy-governance-and-incident-disclosure (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) - 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) - ICO, Personal data breaches: a guide: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/ --- # How the incident response plan template set was made Method, read 16 November 2026 **The short answer.** Each template is our own text, built from one set of fifteen plan sections and checked against the sources named on its page. Company-type versions add a table of rules, each with its source and read date. Word and PDF files are generated from the same text. Edition 16 November 2026. ## How was each template written? Each plan is assembled from a shared library of section texts. The core sections follow the structure that NIST SP 800-61 Rev. 3 and CISA's playbook describe. The company-type versions insert an addendum after the legal notices section; each row cites the rule it summarizes. The playbooks follow a six-part layout adapted from the way Microsoft structures its public playbooks (prerequisites, workflow, checklist, investigation steps), with decision points and exit criteria added. ## How are the Word and PDF files made? A script reads the section text and writes each Word file as a minimal Office Open XML package with Python's zipfile module: a content types file, a relationships file, the document with headings, paragraphs and tables, and a styles file. It then parses every part to confirm the XML is well formed. A second script prints the same text as a print-friendly page to PDF with the Playwright browser library. ## What was checked, and what was left out? - Every rule row was read from the rule text or the issuing agency on 16 November 2026. - A company type has a version only where a rule read for this site makes its needs distinct. Manufacturing and nonprofit organizations have no version: no distinct rule was read for them. - Australian templates are not offered. The OAIC and ACSC pages could not be loaded on the read date. - State breach notification statutes are not summarized: no state statute was read. The school template points to the PTAC checklist, which says most states have such laws. - An AI-incident playbook is not offered: no primary source was read for it. ## How do I cite the set? Cite the set by name and edition, and link to the page. The data files carry the same line. **Cite this.** Incident Response Plan Templates, "Incident Response Plan Template Set", edition 16 November 2026. Data: [CSV](/datasets/incident-response-template-set.csv), [JSON](/datasets/incident-response-template-set.json). ## Related - [The template set](/templates/) - [Site method](/method/) - [How the standards map was read](/standards-map/method/) - [Editorial policy](/editorial-policy/) ## Related pages - [Incident response plan templates: the full set](/templates/) - [Free incident response plan template](/) - [Incident response playbook: what it is and how to build a library](/playbooks/) - [Incident response plan: what it contains and how to build one](/plans/) ## 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) - 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) - Microsoft Learn, Incident response playbooks overview: https://learn.microsoft.com/en-us/security/operations/incident-response-playbooks (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/templates/method/ --- # Which NIST and ISO clauses does each incident response plan section answer? Standards map, read 16 November 2026 **The short answer.** The standards map ties each of the fifteen plan sections to NIST CSF 2.0 outcomes such as RS.MA-03, ISO/IEC 27001:2022 Annex A control numbers 5.24 to 5.28 and 6.8, the ISO/IEC 27035 phases, CISA playbook phases and SANS phases. Edition 16 November 2026; downloadable as CSV and JSON. ## Which standards does each plan section answer? The table below is the map. The NIST column uses the outcomes that NIST SP 800-61 Rev. 3 (April 2025) assigns to incident response. The ISO/IEC 27001:2022 column gives Annex A control numbers that NIST lists as informative references for those outcomes. | Plan section | NIST CSF 2.0 outcomes | ISO/IEC 27001:2022 Annex A control numbers | ISO/IEC 27035 | CISA playbook phase | SANS phase | | --- | --- | --- | --- | --- | --- | | 1. Purpose, scope and authority | GV.PO-01, GV.PO-02, ID.IM-04, GV.RR-02 | 5.1, 5.24, 5.26, 5.27 | Part 1, 5.2 plan and prepare. Part 2 abstract: incident management policy and commitment of top management; incident management plan | Preparation: policies and procedures | 2 Preparation: policy | | 2. Roles and responsibilities | GV.RR-01, GV.RR-02, PR.AT-02 | 5.2, 5.4, 6.3 | Part 1, 5.2 plan and prepare. Part 2 abstract: Incident Management Team establishment | Preparation: trained response personnel; coordination lead | 2 Preparation: team and roles | | 3. Contact and escalation sheet | RS.CO-02, RS.CO-03, GV.SC-08 | 5.26 | Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with internal and external organizations | Preparation: communications and logistics | 2 Preparation: communication | | 4. Severity levels | RS.MA-03, DE.AE-04, RS.AN-08 | 5.25 | Part 1, assessment and decisions phase (clause number not read) | Detection and analysis: determine scope and type | 2 Preparation: response plan, prioritization by impact | | 5. Detecting, reporting and declaring an incident | DE.CM-01, DE.AE-02, DE.AE-03, DE.AE-06, DE.AE-08, RS.MA-02 | 5.24, 5.25, 5.26, 5.27, 5.28, 6.8, 8.15, 8.16 | Part 1, detection and reporting phase (clause number not read) | Detection and analysis: declare incident | 3 Identification | | 6. Triage and analysis | RS.MA-02, RS.MA-03, RS.AN-03, RS.AN-08, DE.AE-04 | 5.24, 5.25, 5.26, 5.27, 5.28, 6.8 | Part 1, assessment and decisions phase (clause number not read) | Detection and analysis: collect and preserve data; determine scope | 3 Identification | | 7. Containment | RS.MI-01, RS.MA-04 | 5.26 | Part 1, responses phase (clause number not read) | Containment | 4 Containment | | 8. Eradication and recovery | RS.MI-02, RS.MA-05, RC.RP-01, RC.RP-02, RC.RP-03, RC.RP-04, RC.RP-05, RC.RP-06 | 5.25, 5.26, 5.27, 8.13 | Part 1, responses phase (clause number not read) | Eradication and recovery | 5 Eradication and 6 Recovery | | 9. Communications | RS.CO-02, RS.CO-03, RC.CO-03, RC.CO-04 | 5.26, 5.28 | Part 1, reporting and responses phases (clause numbers not read) | Coordination | 2 Preparation: communication; 3 Identification: notify the team | | 10. Legal, regulatory, contractual and insurance notices | GV.OC-03, RS.CO-02 | 5.20, 5.26, 5.31 | Part 1, 5.2 plan and prepare (legal and regulatory context; clause detail not read) | Post-incident activities: finalize reports as required by law and policy | 2 Preparation: communication, law enforcement | | 11. Evidence handling and documentation | RS.AN-06, RS.AN-07 | 5.28 | Part 1, assessment and responses phases (clause numbers not read) | Detection and analysis: collect and preserve data | 2 Preparation: documentation; 3 Identification | | 12. Third parties and suppliers | GV.SC-08, DE.CM-06, RS.MA-01 | 5.22, 5.26, 5.27, 5.28, 8.16 | Part 1, 5.2 plan and prepare. Part 2 abstract: relationships with external organizations | Coordination; eradication: coordinate with ICT service providers | 2 Preparation: communication | | 13. Post-incident review | ID.IM-03, ID.IM-04, RC.RP-06 | 5.24, 5.26, 5.27, 8.13 | Part 1, 5.6 learn lessons. Part 2 abstract: identify and make improvements; Incident Response Team evaluation | Post-incident activities: perform hotwash | 7 Lessons Learned | | 14. Testing, training and keeping the plan current | ID.IM-02, ID.IM-04, PR.AT-02, GV.PO-02 | 5.1, 5.2, 5.19, 5.24, 5.26, 5.27, 5.35, 6.3 | Part 1, 5.2 plan and prepare. Part 2 abstract: awareness briefings and training | Preparation: trained response personnel; COOP testing | 2 Preparation: training | | 15. Appendices: forms | RS.AN-06, RC.RP-06 | 5.27, 5.28, 8.13 | Part 1, assessment and lessons phases (clause numbers not read) | Appendix B: incident response checklist | 8 Incident Handlers Checklist | Plan sections mapped to standards ## What do the CSF outcome codes mean? Each code is a CSF 2.0 outcome. The prefix is the Function (GV Govern, ID Identify, PR Protect, DE Detect, RS Respond, RC Recover) and the next two letters the category, for example RS.MA is Incident Management. | Outcome | Text (NIST CSF 2.0) | | --- | --- | | GV.PO-01 | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced | | GV.PO-02 | Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission | | ID.IM-04 | Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improved | | GV.RR-02 | Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced | | GV.RR-01 | Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving | | PR.AT-02 | Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind | | RS.CO-02 | Internal and external stakeholders are notified of incidents | | RS.CO-03 | Information is shared with designated internal and external stakeholders | | GV.SC-08 | Relevant suppliers and other third parties are included in incident planning, response, and recovery activities | | RS.MA-03 | Incidents are categorized and prioritized | | DE.AE-04 | The estimated impact and scope of adverse events are understood | | RS.AN-08 | An incident's magnitude is estimated and validated | | DE.CM-01 | Networks and network services are monitored to find potentially adverse events | | DE.AE-02 | Potentially adverse events are analyzed to better understand associated activities | | DE.AE-03 | Information is correlated from multiple sources | | DE.AE-06 | Information on adverse events is provided to authorized staff and tools | | DE.AE-08 | Incidents are declared when adverse events meet the defined incident criteria | | RS.MA-02 | Incident reports are triaged and validated | | RS.AN-03 | Analysis is performed to establish what has taken place during an incident and the root cause of the incident | | RS.MI-01 | Incidents are contained | | RS.MA-04 | "Incidents are escalated or elevated as needed" | | RS.MI-02 | Incidents are eradicated | | RS.MA-05 | The criteria for initiating incident recovery are applied | | RC.RP-01 | The recovery portion of the incident response plan is executed once initiated from the incident response process | | RC.RP-02 | Recovery actions are selected, scoped, prioritized, and performed | | RC.RP-03 | The integrity of backups and other restoration assets is verified before using them for restoration | | RC.RP-04 | Critical mission functions and cybersecurity risk management are considered to establish post-incident operational norms | | RC.RP-05 | The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed | | RC.RP-06 | The end of incident recovery is declared based on criteria, and incident-related documentation is completed | | RC.CO-03 | Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders | | RC.CO-04 | Public updates on incident recovery are shared using approved methods and messaging | | GV.OC-03 | Legal, regulatory, and contractual requirements regarding cybersecurity, including privacy and civil liberties obligations, are understood and managed | | RS.AN-06 | Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved | | RS.AN-07 | Incident data and metadata are collected, and their integrity and provenance are preserved | | DE.CM-06 | External service provider activities and services are monitored to find potentially adverse events | | RS.MA-01 | The incident response plan is executed in coordination with relevant third parties once an incident is declared | | ID.IM-03 | Improvements are identified from execution of operational processes, procedures, and activities | | ID.IM-02 | Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties | CSF 2.0 outcomes used ## Which CSF categories are covered? The plan draws on categories from five Functions. Incident Management (RS.MA), Incident Analysis (RS.AN), Incident Response Reporting and Communication (RS.CO), Incident Mitigation (RS.MI) and Incident Recovery Plan Execution (RC.RP) carry most of the response work. | Category | Name | | --- | --- | | GV.OC | Organizational Context | | GV.RR | Roles, Responsibilities, and Authorities | | GV.PO | Policy | | GV.SC | Cybersecurity Supply Chain Risk Management | | ID.IM | Improvement | | PR.AT | Awareness and Training | | DE.CM | Continuous Monitoring | | DE.AE | Adverse Event Analysis | | RS.MA | Incident Management | | RS.AN | Incident Analysis | | RS.CO | Incident Response Reporting and Communication | | RS.MI | Incident Mitigation | | RC.RP | Incident Recovery Plan Execution | | RC.CO | Incident Recovery Communication | Categories used **Cite this.** Incident Response Plan Templates, "Incident Response Plan Standards Map", edition 16 November 2026, https://incidentresponseplantemplates.com/standards-map/. Data: [CSV](/datasets/incident-response-standards-map.csv), [JSON](/datasets/incident-response-standards-map.json). ## Related - [How the standards map was read](/standards-map/method/) - [The general template](/) - [Incident response plan guide](/plans/) - [NIST layout template](/templates/incident-response-plan-template-nist/) - [Datasets](/datasets/) ## Related pages - [Free incident response plan template](/) - [The template set](/templates/) - [Datasets](/datasets/) - [Incident response plan guide](/plans/) ## 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) - 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) - ISO/IEC 27035-1:2023 on iso.org: https://www.iso.org/standard/78973.html (read 16 November 2026) - ISO/IEC 27035-2:2023 on iso.org: https://www.iso.org/standard/78974.html (read 16 November 2026) - ISO/IEC 27001:2022 on iso.org: https://www.iso.org/standard/82875.html (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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/standards-map/ --- # How the incident response standards map was read Method, read 16 November 2026 **The short answer.** The map uses NIST SP 800-61 Rev. 3 (April 2025) for CSF 2.0 outcomes, and NIST's CSF 2.0 Reference Tool for ISO/IEC 27001:2022 Annex A control numbers. ISO/IEC 27035 clause lists could not be read, so only the clause numbers and phase names printed on iso.org are used. Read 16 November 2026. ## What exactly was read? Six documents were read in full or in the parts that matter, on 16 November 2026. The table lists each with the identifier or date read and what it was used for. | Document | Identifier or date read | Used for | | --- | --- | --- | | NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile | Published April 2025 (final 3 April 2025); DOI 10.6028/NIST.SP.800-61r3; supersedes Rev. 2 of 6 August 2012 | CSF Function and category structure, outcome text (Tables 2 and 3), roles, policy elements | | NIST CSF 2.0 Reference Tool download | Informative references to ISO/IEC 27001:2022 per CSF 2.0 subcategory, read 16 November 2026 | Annex A control numbers (5.24 to 5.28, 6.8, 8.13 and others) | | ISO/IEC 27035-1:2023 and 27035-2:2023, iso.org pages | Edition 2, published February 2023; 33 and 53 pages | Phase names and the clause numbers 5.2 and 5.6, as printed in the 27035-2 abstract | | ISO/IEC 27001:2022, iso.org page | Published 2022 | Confirms the Annex A numbering context | | CISA Cybersecurity Incident & Vulnerability Response Playbooks | Publication November 2021 (federal agencies) | Phase names: preparation; detection and analysis; containment; eradication and recovery; post-incident activities; coordination | | SANS Incident Handler's Handbook | Published 21 February 2012 | Six phases: preparation, identification, containment, eradication, recovery, lessons learned | Documents read ## Which ISO clause numbers could not be read? The ISO Online Browsing Platform preview did not load on the read date, so the clause lists of ISO/IEC 27035-1:2023 and 27035-2:2023 were not read. Only what iso.org prints on the standard pages is used: the 27035-2 abstract says its guidance is based on the "plan and prepare" and "learn lessons" phases presented in ISO/IEC 27035-1:2023, 5.2 and 5.6. The map therefore gives clause numbers 5.2 and 5.6 only, and names the other phases (detection and reporting, assessment and decisions, responses) without clause numbers. ISO/IEC 27001:2022 Annex A control titles were also not read from a page, so the data carries control numbers only, as NIST lists them. Annex A 5.24 to 5.28 and 6.8 appear in the map through those NIST references. ## How was each plan section mapped? Each plan section was matched to the CSF 2.0 outcomes whose text it answers, such as RS.MA-02 (incident reports are triaged and validated) for triage. The ISO column is the union of the Annex A numbers NIST lists for those outcomes. The CISA and SANS columns name the nearest phase in each document. The mapping is our judgment, and the data lets you check it row by row. **Cite this.** Incident Response Plan Templates, "Incident Response Plan Standards Map", edition 16 November 2026. Data: [CSV](/datasets/incident-response-standards-map.csv), [JSON](/datasets/incident-response-standards-map.json). ## Related - [The standards map](/standards-map/) - [How the template set was made](/templates/method/) - [Site method](/method/) - [Glossary](/glossary/) ## Related pages - [Free incident response plan template](/) - [The template set](/templates/) - [The standards map](/standards-map/) - [Datasets](/datasets/) - [Incident response plan guide](/plans/) ## Sources - NIST SP 800-61 Rev. 3, publication page (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 16 November 2026) - 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) - 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) - ISO/IEC 27035-1:2023 on iso.org: https://www.iso.org/standard/78973.html (read 16 November 2026) - ISO/IEC 27035-2:2023 on iso.org: https://www.iso.org/standard/78974.html (read 16 November 2026) - ISO/IEC 27001:2022 on iso.org: https://www.iso.org/standard/82875.html (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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/standards-map/method/ --- # How Incident Response Plan Templates sources its facts Method, read 16 November 2026 **The short answer.** Facts about rules, standards and agency guidance were read from the issuing source on 16 November 2026. Facts about firms were read on 10 November 2026 from the firms' own pages, a brochure or a named analyst report. Each page prints the source address and read date. ## How are facts sourced? Facts about a rule, standard or agency guidance are read from the issuing source and printed with its address and read date. Frameworks come from NIST, CISA, the NCSC and the SANS Institute; rules from the eCFR, the Federal Register, EUR-Lex, Cornell LII and regulators' own pages; firms from their own pages, a brochure or the analyst report named in the fact. Templates are our own writing. They are not legal advice. Each company-type version names the rule that makes it distinct. ## What could not be read? - ISO Online Browsing Platform clause lists for ISO/IEC 27035-1 and 27035-2: the preview did not load. - OAIC (Australia) and ACSC pages: access was refused on the read date, so no Australian template is offered. - FTC and HHS guidance pages and the SEC web pages: access was refused. The rule text was read from the eCFR and the Federal Register instead. - State breach notification statutes: not read. - A source for AI-specific incident response: none read. ## How are firms treated? The [services page](/services/) lists sixteen firms in alphabetical order with the same fields for each. The firm facts were read on 10 November 2026, from the firms' own pages, one brochure (Sophos, for Secureworks) and one analyst report (IDC, for Arctic Wolf); the Cisco Talos, CrowdStrike, Unit 42 and Sygnia cells were re-read on 16 November 2026. Sygnia's pages were read through its mirror cdn.sygnia.co because sygnia.co refused the reader; links point to sygnia.co. Nothing is scored, ranked or rated. ## How often is it reviewed? Pages carry a review date. Facts older than 60 days are re-read before they are reused. See the [editorial policy](/editorial-policy/) and [corrections](/corrections/). ## Related - [How the template set was made](/templates/method/) - [How the standards map was read](/standards-map/method/) - [Glossary](/glossary/) - [FAQ](/faq/) - [Datasets](/datasets/) ## Related pages - [Free incident response plan template](/) - [The template set](/templates/) - [The standards map](/standards-map/) - [Datasets](/datasets/) - [Incident response plan guide](/plans/) ## Sources - NIST SP 800-61 Rev. 3, publication page (April 2025): https://csrc.nist.gov/pubs/sp/800/61/r3/final (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) - 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) - SANS Institute, Incident Handler's Handbook (21 February 2012): https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/method/ --- # Datasets: the template set and the standards map Datasets, read 16 November 2026 **In short.** Two datasets, edition 16 November 2026, under CC BY 4.0: the template set (21 templates with sections, rules and file addresses) and the standards map (fifteen plan sections mapped to NIST CSF 2.0, ISO/IEC 27001 Annex A numbers, ISO/IEC 27035, CISA and SANS). Each is a CSV and a JSON file. | Dataset | Rows | CSV | JSON | | --- | --- | --- | --- | | Incident Response Plan Template Set | 21 | [csv](/datasets/incident-response-template-set.csv) | [json](/datasets/incident-response-template-set.json) | | Incident Response Plan Standards Map | 189 | [csv](/datasets/incident-response-standards-map.csv) | [json](/datasets/incident-response-standards-map.json) | Datasets The plan builder data, which lists the plan sections for every pairing of company type and incident type, is a separate file: [plan-builder.json](/data/plan-builder.json). The section text it points to is in [plan-sections.json](/data/plan-sections.json). **Cite this.** Incident Response Plan Templates, edition 16 November 2026, https://incidentresponseplantemplates.com/datasets/. License CC BY 4.0. ## Related - [The template set](/templates/) - [The standards map](/standards-map/) - [Template set method](/templates/method/) - [Standards map method](/standards-map/method/) ## Related pages - [Free incident response plan template](/) - [The template set](/templates/) - [The standards map](/standards-map/) - [Incident response plan guide](/plans/) ## 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) - 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/datasets/ --- # Who offers incident response planning as a service? Services, read 16 November 2026 **The short answer.** Sixteen incident response firms are listed alphabetically with the same three fields: plan development or review, tabletop exercises and playbooks. Each cell states what the firm's own page or a named analyst report says, or "none found". Facts were read on 10 and 16 November 2026. Nobody is ranked or scored. ## Which firms offer incident response planning? Most firms in this set list some planning or exercise service, usually alongside a retainer. The table shows what each says. "None found" means the page named in the cell does not say the firm offers it, not that the firm offers nothing. One test applies to every firm: a service is reported only if a page says the firm offers it. | Firm | Plan development or review | Tabletop exercises | Playbooks | Facts read | | --- | --- | --- | --- | --- | | Arctic Wolf | IDC says Arctic Wolf offers an IR Plan Builder that collects the information needed to start an IR investigation, and that its Incident Response team can access the stored plan during attacks. ([analyst report](https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment)) | None found on the page read: [arcticwolf.com/solutions/incident-response](https://arcticwolf.com/solutions/incident-response/). | None found on the page read: [arcticwolf.com/solutions/incident-response](https://arcticwolf.com/solutions/incident-response/). | 10 Nov 2026 | | Booz Allen Hamilton | Its cybersecurity strategy page lists board-level cyber exercises and incident response and pre-incident planning among its solutions, and says that in a cyber attack the firm is the client's advocate and instrument for incident response and business recovery. ([firm page](https://www.boozallen.com/markets/commercial-solutions/cybersecurity-strategy.html)) | Its incident response capabilities list includes cloud compromise investigations, mobile device forensics, insider threat investigations, emergency staff augmentation and tabletop exercises and wargaming. ([firm page](https://www.boozallen.com/markets/commercial-solutions/incident-response.html)) | None found on the page read: [boozallen.com/markets/commercial-solutions/cybersecurity-strategy.html](https://www.boozallen.com/markets/commercial-solutions/cybersecurity-strategy.html). | 10 Nov 2026 | | Charles River Associates | The retainer program described includes response plans, regular testing and on-demand forensic expert access; no prepaid hours, minimums or conversion terms are published. ([firm page](https://www.crai.com/services/information-security-and-privacy/cybersecurity/incident-response/)) | None found on the page read: [crai.com/services/information-security-and-privacy/cybersecurity/incident-response](https://www.crai.com/services/information-security-and-privacy/cybersecurity/incident-response/). | None found on the page read: [crai.com/services/information-security-and-privacy/cybersecurity/incident-response](https://www.crai.com/services/information-security-and-privacy/cybersecurity/incident-response/). | 10 Nov 2026 | | Check Point Incident Response | The IR page lists incident response plan development and table-top exercises among its services. ([firm page](https://www.checkpoint.com/services/incident-response/)) | Same statement as in the column to its left ([firm page](https://www.checkpoint.com/services/incident-response/)). | None found on the page read: [checkpoint.com/services/incident-response](https://www.checkpoint.com/services/incident-response/). | 10 Nov 2026 | | Cisco Talos Incident Response | The services page lists an IR Plan service: "Develop a customized plan to support coordinated response and communications during a cybersecurity incident", and says Talos IR can also review an existing plan. ([firm page](https://talosintelligence.com/incident_response/services)) | The services page lists Tabletop Exercises: "Partner with Talos IR to test your current IR plan, playbooks and tactics, techniques and procedures with real-world scenarios in a controlled, collaborative setting". ([firm page](https://talosintelligence.com/incident_response/services)) | The services page lists IR Playbooks: "Create detailed documentation with step-by-step processes for responding to the most relevant threats to your organization". ([firm page](https://talosintelligence.com/incident_response/services)) | 16 Nov 2026 | | Coveware | None found on the page read: coveware.com/retained-services. | The firm says retained clients can subscribe to a Bespoke Service package for a customized tabletop or hands-on ransomware preparation workshops, and the second package includes one bespoke exercise per year. (firm page) | None found on the page read: coveware.com/retained-services. | 10 Nov 2026 | | CrowdStrike | None found on the tabletop exercise page or the incident response page. ([page 1](https://www.crowdstrike.com/en-us/services/prepare/tabletop-exercise/), [page 2](https://www.crowdstrike.com/en-us/services/incident-response/)) | The tabletop exercise page describes a discussion-based exercise built on an incident scenario for the client's environment, led by the services team, with a summary report and a prioritized list of takeaways. ([firm page](https://www.crowdstrike.com/en-us/services/prepare/tabletop-exercise/)) | None found on the tabletop exercise page or the incident response page. ([page 1](https://www.crowdstrike.com/en-us/services/prepare/tabletop-exercise/), [page 2](https://www.crowdstrike.com/en-us/services/incident-response/)) | 16 Nov 2026 | | IBM X-Force | The datasheet lists cyber crisis management as a retainer proactive service, described as a whole-of-business framework with program assessment, playbooks and tabletop exercises. ([firm page](https://www.ibm.com/downloads/cas/NQOVED3M)) | Same statement as in the column to its left ([firm page](https://www.ibm.com/downloads/cas/NQOVED3M)). | Same statement as in the column to its left ([firm page](https://www.ibm.com/downloads/cas/NQOVED3M)). | 10 Nov 2026 | | Kroll | None found. The incident response page lists strategic communications support, preparedness and training, and remediation and recovery, but not plan development. ([page 1](https://www.kroll.com/en/services/cyber/reactive-services/incident-response)) | None found on the page read: [kroll.com/en/services/cyber/reactive-services/incident-response](https://www.kroll.com/en/services/cyber/reactive-services/incident-response). | None found on the page read: [kroll.com/en/services/cyber/reactive-services/incident-response](https://www.kroll.com/en/services/cyber/reactive-services/incident-response). | 10 Nov 2026 | | Mandiant (Google Cloud) | None found on the page read: [cloud.google.com/security/consulting/mandiant-retainer](https://cloud.google.com/security/consulting/mandiant-retainer). | The retainer FAQ lists readiness assessments, tabletop exercises, penetration testing and training as proactive uses of unused hours. ([firm page](https://cloud.google.com/security/consulting/mandiant-retainer)) | The firm says its crisis communications service builds playbooks so legal, executive and technical teams work from one message. ([firm page](https://cloud.google.com/security/consulting/mandiant-incident-response-services)) | 10 Nov 2026 | | Microsoft | Its capabilities list covers investigation, containment/recovery/eviction, planning, assessment, simulation and advisory services. ([firm page](https://www.microsoft.com/en-us/security/business/microsoft-defender-experts-cybersecurity-incident-response)) | Same statement as in the column to its left ([firm page](https://www.microsoft.com/en-us/security/business/microsoft-defender-experts-cybersecurity-incident-response)). | None found on the page read: [microsoft.com/en-us/security/business/microsoft-defender-experts-cybersecurity-incident-response](https://www.microsoft.com/en-us/security/business/microsoft-defender-experts-cybersecurity-incident-response). | 10 Nov 2026 | | Mitiga | Lemonade's CISO describes receiving a readiness assessment and two tabletop exercises from Mitiga, and a compromise assessment during an acquisition; no retainer terms, hours or price are stated. ([firm page](https://www.mitiga.io/resources/lemonade-chooses-mitiga-for-cloud-incident-readiness-and-response)) | Same statement as in the column to its left ([firm page](https://www.mitiga.io/resources/lemonade-chooses-mitiga-for-cloud-incident-readiness-and-response)). | None found on the page read: [mitiga.io/resources/lemonade-chooses-mitiga-for-cloud-incident-readiness-and-response](https://www.mitiga.io/resources/lemonade-chooses-mitiga-for-cloud-incident-readiness-and-response). | 10 Nov 2026 | | NCC Group | None found on the page read: [nccgroup.com/incident-response](https://www.nccgroup.com/incident-response/). | Its incident response page describes services spanning intake, identification, analysis, containment and remediation, plus tabletop simulations and first responder training. ([firm page](https://www.nccgroup.com/incident-response/)) | None found on the page read: [nccgroup.com/incident-response](https://www.nccgroup.com/incident-response/). | 10 Nov 2026 | | Palo Alto Networks Unit 42 | The tabletop page says the exercise runs simulated incidents "to test your documented plan" and interviews stakeholders to confirm procedures match practice. It does not describe writing a new plan. ([firm page](https://www.paloaltonetworks.com/unit42/assess/tabletop-exercise)) | The page says Unit 42 facilitates an interactive tabletop exercise, remote or in person, for technical or executive audiences, with an after-action report and prioritized recommendations. ([firm page](https://www.paloaltonetworks.com/unit42/assess/tabletop-exercise)) | The tabletop page says the exercise can "validate your IR playbooks against the latest threats". It does not describe writing new playbooks. ([firm page](https://www.paloaltonetworks.com/unit42/assess/tabletop-exercise)) | 16 Nov 2026 | | Secureworks | None found on the page read: [assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf](https://assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf). | A Sophos brochure (Sophos owns Secureworks) says Service Units can be redeemed for penetration tests, assessments, tabletop exercises and Sophos product implementation as well as converted to DFIR hours. ([firm page](https://assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf)) | None found on the page read: [assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf](https://assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf). | 10 Nov 2026 | | Sygnia | None found. The Services menu lists no plan development item, and the retainer page says only that the retainer gives access to its preparedness services. ([page 1](https://www.sygnia.co/?utm_source=incidentresponseplantemplates.com&utm_medium=referral&utm_campaign=directory), [page 2](https://www.sygnia.co/solutions/incident-response-retainer/?utm_source=incidentresponseplantemplates.com&utm_medium=referral&utm_campaign=directory)) | The Services menu lists Tabletop Exercises under Cyber Readiness. The page describes a leadership tabletop led by Sygnia experts, about two to three hours, followed by a debrief and an action list. ([firm page](https://www.sygnia.co/solutions/cyber-war-gaming/?utm_source=incidentresponseplantemplates.com&utm_medium=referral&utm_campaign=directory)) | None found in the Services menu or on the tabletop exercise page. ([page 1](https://www.sygnia.co/?utm_source=incidentresponseplantemplates.com&utm_medium=referral&utm_campaign=directory), [page 2](https://www.sygnia.co/solutions/cyber-war-gaming/?utm_source=incidentresponseplantemplates.com&utm_medium=referral&utm_campaign=directory)) | 16 Nov 2026 | Firms in alphabetical order. Same fields for every firm. ## What should you ask any provider about planning? Ask four questions before you sign. They turn a general offer of planning help into terms you can check. - Will the provider work from your template, or insist on its own? - Who writes the notice rules table, and who confirms it with counsel? - Is an exercise included in a retainer, and are unused hours usable for it? - Will the provider be named in your plan as a third party, with its contact and authority to act? NIST asks that suppliers be included in incident planning (outcome GV.SC-08). See the [roles page](/plans/incident-response-roles-and-responsibilities/) for how outside providers fit, and the [third-party playbook](/playbooks/third-party-incident-response-playbook/). ## Related pages - [Free incident response plan template](/) - [The template set](/templates/) - [The standards map](/standards-map/) - [Datasets](/datasets/) - [Incident response plan guide](/plans/) ## 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) - Arctic Wolf (analyst report): https://arcticwolf.com/resource/aw/idc-marketscape-worldwide-managed-detection-and-response-2024-vendor-assessment (read 10 November 2026) - Booz Allen Hamilton (firm page): https://www.boozallen.com/markets/commercial-solutions/cybersecurity-strategy.html (read 10 November 2026) - Booz Allen Hamilton (firm page): https://www.boozallen.com/markets/commercial-solutions/incident-response.html (read 10 November 2026) - Charles River Associates (firm page): https://www.crai.com/services/information-security-and-privacy/cybersecurity/incident-response/ (read 10 November 2026) - Check Point Incident Response (firm page): https://www.checkpoint.com/services/incident-response/ (read 10 November 2026) - Cisco Talos Incident Response (firm page): https://talosintelligence.com/incident_response/services (read 10 November 2026) - IBM X-Force (firm page): https://www.ibm.com/downloads/cas/NQOVED3M (read 10 November 2026) - Kroll (firm page): https://www.kroll.com/en/services/cyber/reactive-services/incident-response (read 10 November 2026) - Mandiant (Google Cloud) (firm page): https://cloud.google.com/security/consulting/mandiant-retainer (read 10 November 2026) - Mandiant (Google Cloud) (firm page): https://cloud.google.com/security/consulting/mandiant-incident-response-services (read 10 November 2026) - Microsoft (firm page): https://www.microsoft.com/en-us/security/business/microsoft-defender-experts-cybersecurity-incident-response (read 10 November 2026) - Mitiga (firm page): https://www.mitiga.io/resources/lemonade-chooses-mitiga-for-cloud-incident-readiness-and-response (read 10 November 2026) - NCC Group (firm page): https://www.nccgroup.com/incident-response/ (read 10 November 2026) - Secureworks (firm page): https://assets.sophos.com/X24WTUEQ/at/6s69xwv3xkkjsbnv4m7wffpc/sophos-security-services-retainer-br.pdf (read 10 November 2026) - Sygnia (firm page) via cdn.sygnia.co: https://www.sygnia.co/solutions/incident-response-retainer/ (read 10 November 2026) - Sygnia (firm page) via cdn.sygnia.co: https://www.sygnia.co/ (read 10 November 2026) - CrowdStrike (firm page): https://www.crowdstrike.com/en-us/services/prepare/tabletop-exercise/ (read 16 November 2026) - CrowdStrike (firm page): https://www.crowdstrike.com/en-us/services/incident-response/ (read 16 November 2026) - Palo Alto Networks Unit 42 (firm page): https://www.paloaltonetworks.com/unit42/assess/tabletop-exercise (read 16 November 2026) - Sygnia (firm page) via cdn.sygnia.co: https://www.sygnia.co/solutions/cyber-war-gaming/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/services/ --- # 22 incident response terms, each with a sourced example Glossary, read 16 November 2026 **In short.** 22 terms from incident response planning, from incident declaration and containment to HIPAA breach and NIS2 early warning. Each has a plain definition and an example quoted from NIST, CISA, SANS, the NCSC or the rule text, with the read date. ## What do incident response terms mean? These 22 terms are the words a plan uses. Each entry defines the term in plain language and quotes a source. Start with the incident response plan, the policy and the playbook. - [Breach (HIPAA)](/glossary/breach-hipaa/): Under the HIPAA rule, the acquisition, access, use or sharing of protected health information in a way the rul - [Business email compromise](/glossary/business-email-compromise/): A scam in which someone controls or imitates a business email account to trick staff into sending money or sen - [Containment](/glossary/containment/): Actions that stop an incident from spreading or causing more damage, taken without destroying evidence. - [DDoS attack](/glossary/ddos-attack/): A distributed denial-of-service attack floods a service with traffic from many sources so that legitimate user - [Early warning (NIS2)](/glossary/early-warning-nis2/): The first report an essential or important entity makes under NIS2, due within 24 hours of becoming aware of a - [Eradication](/glossary/eradication/): Removing the cause of an incident, such as malicious code and attacker access, and fixing the condition that w - [Escalation](/glossary/escalation/): Raising an incident to a higher level of attention or authority when its severity or impact grows. - [Hotwash](/glossary/hotwash/): A lessons-learned review held after an incident to find what worked, what failed and what to change. - [Incident declaration](/glossary/incident-declaration/): The decision that an event meets the defined incident criteria and that the plan is now in force - [Incident handler](/glossary/incident-handler/): A person, on staff, on contract or available when needed, who confirms an incident, analyzes evidence, sets pr - [Incident response plan](/glossary/incident-response-plan/): A written document that sets roles, authorities, severity rules, contacts and steps for handling cybersecurity - [Incident response policy](/glossary/incident-response-policy/): The high-level statement of management commitment, purpose, scope, definitions, authorities and measures that - [Insider threat](/glossary/insider-threat/): The potential for a person with authorized access to use that access to harm the organization, on purpose or b - [Jump bag](/glossary/jump-bag/): A kit of tools, checklists and contact lists that responders can grab at once when an incident is declared. - [Material cybersecurity incident](/glossary/material-cybersecurity-incident/): A cybersecurity incident a public company has determined to be material - [Playbook](/glossary/playbook/): A set of actionable steps for people to follow in one scenario, such as phishing - [Procedure](/glossary/procedure/): A documented description of how a technical or operating task is performed - [Recovery](/glossary/recovery/): Restoring affected systems and services to normal operation and confirming they work and are clean. - [Severity level](/glossary/severity-level/): A rating of an incident's impact on the organization that decides who is called and how fast. - [Significant incident (NIS2)](/glossary/significant-incident-nis2/): Under the EU NIS2 Directive, an incident that has caused or can cause severe operational disruption or financi - [Triage](/glossary/triage/): The first review of an incident report to confirm it is real and to decide how urgent it is. - [Unsecured protected health information](/glossary/unsecured-phi/): Protected health information that has not been made unusable, unreadable or indecipherable to unauthorized peo ## Related pages - [FAQ](/faq/) - [Incident response plan guide](/plans/) - [Free incident response plan template](/) - [Incident response steps](/steps/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/ --- # Breach (HIPAA), defined Glossary term, read 16 November 2026 **The short answer.** Under the HIPAA rule a breach is an impermissible acquisition, access, use or sharing of protected health information that compromises its security or privacy, presumed unless a risk assessment shows a low probability of compromise. The rule names four risk factors. This entry was read on 16 November 2026 from 45 CFR 164.402. ## What is a breach under HIPAA? Under the HIPAA rule, the acquisition, access, use or sharing of protected health information in a way the rules do not permit and that compromises its security or privacy. It is presumed unless a risk assessment shows a low probability of compromise. ## Definition Under the HIPAA rule, the acquisition, access, use or sharing of protected health information in a way the rules do not permit and that compromises its security or privacy. It is presumed unless a risk assessment shows a low probability of compromise. ## A sourced example 45 CFR 164.402 lists the four risk factors: the nature and extent of the information, the unauthorized person, whether it was actually acquired or viewed, and the extent of mitigation (eCFR, read 16 November 2026). ## Related terms - [Business email compromise](/glossary/business-email-compromise/) - [Containment](/glossary/containment/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - ecfr.gov: https://www.ecfr.gov/current/title-45/section-164.402 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/breach-hipaa/ --- # Business email compromise, defined Glossary term, read 16 November 2026 **The short answer.** Business email compromise, or BEC, is a scam in which someone controls or imitates a business email account to trick staff into sending money or information. The FBI IC3 describes it as targeting businesses and individuals who perform transfer-of-funds requests. This entry was read on 16 November 2026. ## What is a business email compromise? A scam in which someone controls or imitates a business email account to trick staff into sending money or sensitive information. ## Definition A scam in which someone controls or imitates a business email account to trick staff into sending money or sensitive information. ## A sourced example The FBI IC3 says BEC "is a sophisticated scam that targets both businesses and individuals who perform legitimate transfer-of-funds requests" (IC3 alert I-091124-PSA, 11 September 2024, read 16 November 2026). ## Related terms - [Breach (HIPAA)](/glossary/breach-hipaa/) - [Containment](/glossary/containment/) - [DDoS attack](/glossary/ddos-attack/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - ic3.gov: https://www.ic3.gov/PSA/2024/PSA240911 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/business-email-compromise/ --- # Containment, defined Glossary term, read 16 November 2026 **The short answer.** Containment is the set of actions that stop an incident from spreading or causing more damage, taken without destroying evidence. CISA's playbook gives its objective as preventing further damage and reducing immediate impact by removing the adversary's access. This entry was read on 16 November 2026. ## What is containment? Actions that stop an incident from spreading or causing more damage, taken without destroying evidence. ## Definition Actions that stop an incident from spreading or causing more damage, taken without destroying evidence. ## A sourced example CISA's playbook says the objective of containment "is to prevent further damage and reduce the immediate impact of the incident by removing the adversary's access" (CISA, November 2021, read 16 November 2026). ## Related terms - [Breach (HIPAA)](/glossary/breach-hipaa/) - [Business email compromise](/glossary/business-email-compromise/) - [DDoS attack](/glossary/ddos-attack/) - [Early warning (NIS2)](/glossary/early-warning-nis2/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - cisa.gov: https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/containment/ --- # DDoS attack, defined Glossary term, read 16 November 2026 **The short answer.** A DDoS attack, short for distributed denial-of-service, floods a service with traffic from many sources so that legitimate users cannot use it. CISA, the FBI and MS-ISAC note that the many sources make the attack hard to trace and block. This entry was read on 16 November 2026. ## What is a DDoS attack? A distributed denial-of-service attack floods a service with traffic from many sources so that legitimate users cannot use it. ## Definition A distributed denial-of-service attack floods a service with traffic from many sources so that legitimate users cannot use it. ## A sourced example CISA, the FBI and MS-ISAC say DDoS attacks "typically originate from multiple sources, making them difficult to trace and effectively block the attacking internet protocol (IP) addresses" (guide of 21 March 2024, read 16 November 2026). ## Related terms - [Business email compromise](/glossary/business-email-compromise/) - [Containment](/glossary/containment/) - [Early warning (NIS2)](/glossary/early-warning-nis2/) - [Eradication](/glossary/eradication/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - cisa.gov: https://www.cisa.gov/sites/default/files/publications/understanding-and-responding-to-ddos-attacks_508c.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/ddos-attack/ --- # Early warning (NIS2), defined Glossary term, read 16 November 2026 **The short answer.** An early warning is the first report an essential or important entity makes under NIS2, due within 24 hours of becoming aware of a significant incident. Article 23(4) then requires an incident notification within 72 hours and a final report within one month. This entry was read on 16 November 2026. ## What is an early warning under NIS2? The first report an essential or important entity makes under NIS2, due within 24 hours of becoming aware of a significant incident. ## Definition The first report an essential or important entity makes under NIS2, due within 24 hours of becoming aware of a significant incident. ## A sourced example NIS2 Article 23(4)(a) requires "an early warning" without undue delay and in any event within 24 hours, then an incident notification within 72 hours and a final report within one month (EUR-Lex, read 16 November 2026). ## Related terms - [Containment](/glossary/containment/) - [DDoS attack](/glossary/ddos-attack/) - [Eradication](/glossary/eradication/) - [Escalation](/glossary/escalation/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - eur-lex.europa.eu: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/early-warning-nis2/ --- # Eradication, defined Glossary term, read 16 November 2026 **The short answer.** Eradication is removing the cause of an incident, such as malicious code and attacker access, and fixing the condition that was exploited. CISA's playbook gives reimaging infected systems as an example and says to account for all persistent access first. This entry was read on 16 November 2026. ## What is eradication? Removing the cause of an incident, such as malicious code and attacker access, and fixing the condition that was exploited. ## Definition Removing the cause of an incident, such as malicious code and attacker access, and fixing the condition that was exploited. ## A sourced example CISA's playbook describes eradication as "eliminating artifacts of the incident (e.g., remove malicious code, re-image infected systems) and mitigating the vulnerabilities or other conditions that were exploited" (read 16 November 2026). ## Related terms - [DDoS attack](/glossary/ddos-attack/) - [Early warning (NIS2)](/glossary/early-warning-nis2/) - [Escalation](/glossary/escalation/) - [Hotwash](/glossary/hotwash/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - cisa.gov: https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/eradication/ --- # Escalation, defined Glossary term, read 16 November 2026 **The short answer.** Escalation is raising an incident to a higher level of attention or authority when its severity or impact grows. NIST CSF 2.0 outcome RS.MA-04 covers escalating incidents as needed. The NCSC advises setting escalation criteria in advance. This entry was read on 16 November 2026. ## What is escalation? Raising an incident to a higher level of attention or authority when its severity or impact grows. ## Definition Raising an incident to a higher level of attention or authority when its severity or impact grows. ## A sourced example NIST CSF 2.0 outcome RS.MA-04 reads "Incidents are escalated or elevated as needed". The NCSC advises setting criteria for escalation to senior management (read 16 November 2026). ## Related terms - [Early warning (NIS2)](/glossary/early-warning-nis2/) - [Eradication](/glossary/eradication/) - [Hotwash](/glossary/hotwash/) - [Incident declaration](/glossary/incident-declaration/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/escalation/ --- # Hotwash, defined Glossary term, read 16 November 2026 **The short answer.** A hotwash is a lessons-learned review held after an incident to find what worked, what failed and what to change. CISA's playbook lists it as a post-incident activity and says to capture lessons learned, initial root cause and missing policies and procedures. This entry was read on 16 November 2026. ## What is a hotwash? A lessons-learned review held after an incident to find what worked, what failed and what to change. ## Definition A lessons-learned review held after an incident to find what worked, what failed and what to change. ## A sourced example CISA's playbook tells agencies to "Conduct a lessons-learned analysis to review the effectiveness and efficiency of incident handling" under the heading Perform Hotwash (read 16 November 2026). ## Related terms - [Eradication](/glossary/eradication/) - [Escalation](/glossary/escalation/) - [Incident declaration](/glossary/incident-declaration/) - [Incident handler](/glossary/incident-handler/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - cisa.gov: https://www.cisa.gov/sites/default/files/2024-08/Federal_Government_Cybersecurity_Incident_and_Vulnerability_Response_Playbooks_508C.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/hotwash/ --- # Incident declaration, defined Glossary term, read 16 November 2026 **The short answer.** Incident declaration is the decision that an event meets the defined incident criteria and that the plan is now in force. It starts the log, the severity rating and the notice clocks. NIST CSF outcome DE.AE-08 states the rule. This entry was read on 16 November 2026. ## What is incident declaration? The decision that an event meets the defined incident criteria and that the plan is now in force. It starts the log, the severity rating and the notice clocks. ## Definition The decision that an event meets the defined incident criteria and that the plan is now in force. It starts the log, the severity rating and the notice clocks. ## A sourced example NIST CSF 2.0 outcome DE.AE-08 reads "Incidents are declared when adverse events meet the defined incident criteria" (read 16 November 2026, NIST SP 800-61 Rev. 3). ## Related terms - [Escalation](/glossary/escalation/) - [Hotwash](/glossary/hotwash/) - [Incident handler](/glossary/incident-handler/) - [Incident response plan](/glossary/incident-response-plan/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/incident-declaration/ --- # Incident handler, defined Glossary term, read 16 November 2026 **The short answer.** An incident handler is a person, on staff, on contract or available when needed, who confirms an incident, analyzes evidence, sets priorities and acts to limit damage and restore service. NIST SP 800-61 Rev. 3, section 2.2, describes the role. This entry was read on 16 November 2026. ## What is an incident handler? A person, on staff, on contract or available when needed, who confirms an incident, analyzes evidence, sets priorities and acts to limit damage and restore service. ## Definition A person, on staff, on contract or available when needed, who confirms an incident, analyzes evidence, sets priorities and acts to limit damage and restore service. ## A sourced example NIST SP 800-61 Rev. 3 says incident handlers "verify that an incident has occurred, collect and analyze data and evidence, prioritize incident response activities, and act appropriately to limit damage, find root causes, and restore operations" (read 16 November 2026). ## Related terms - [Hotwash](/glossary/hotwash/) - [Incident declaration](/glossary/incident-declaration/) - [Incident response plan](/glossary/incident-response-plan/) - [Incident response policy](/glossary/incident-response-policy/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/incident-handler/ --- # Incident response plan, defined Glossary term, read 16 November 2026 **The short answer.** An incident response plan is a written document that sets roles, authorities, severity rules, contacts and steps for handling cybersecurity incidents. NIST SP 800-61 Rev. 3 calls it the roadmap for implementing the incident response capability. This entry was read on 16 November 2026; the example is quoted from NIST. ## What is an incident response plan? A written document that sets roles, authorities, severity rules, contacts and steps for handling cybersecurity incidents. It sits below the policy and above playbooks and procedures. ## Definition A written document that sets roles, authorities, severity rules, contacts and steps for handling cybersecurity incidents. It sits below the policy and above playbooks and procedures. ## A sourced example NIST SP 800-61 Rev. 3 says incident response plans "provide the roadmap for implementing the incident response capability" (note N1 under outcome ID.IM-04, read 16 November 2026). ## Related terms - [Incident declaration](/glossary/incident-declaration/) - [Incident handler](/glossary/incident-handler/) - [Incident response policy](/glossary/incident-response-policy/) - [Insider threat](/glossary/insider-threat/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/incident-response-plan/ --- # Incident response policy, defined Glossary term, read 16 November 2026 **The short answer.** An incident response policy is the high-level statement of management commitment, scope, definitions, authorities and measures that governs incident response, with the plan and procedures built on it. NIST SP 800-61 Rev. 3, section 2.3, lists the usual elements. This entry was read on 16 November 2026. ## What is an incident response policy? The high-level statement of management commitment, purpose, scope, definitions, authorities and measures that governs incident response. The plan and procedures are based on it. ## Definition The high-level statement of management commitment, purpose, scope, definitions, authorities and measures that governs incident response. The plan and procedures are based on it. ## A sourced example NIST SP 800-61 Rev. 3, section 2.3, lists the usual elements: management commitment, purpose and objectives, scope, definitions, roles with authorities, prioritization guidelines and performance measures (read 16 November 2026). ## Related terms - [Incident handler](/glossary/incident-handler/) - [Incident response plan](/glossary/incident-response-plan/) - [Insider threat](/glossary/insider-threat/) - [Jump bag](/glossary/jump-bag/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/incident-response-policy/ --- # Insider threat, defined Glossary term, read 16 November 2026 **The short answer.** An insider threat is the potential for a person with authorized access to use that access to harm the organization, on purpose or by accident. CISA defines an insider as anyone who has or had authorized access to or knowledge of the organization's resources. This entry was read on 16 November 2026. ## What is an insider threat? The potential for a person with authorized access to use that access to harm the organization, on purpose or by accident. ## Definition The potential for a person with authorized access to use that access to harm the organization, on purpose or by accident. ## A sourced example CISA defines an insider as "any person who has or had authorized access to or knowledge of an organization's resources" and insider threat as the potential for an insider to use that access to harm the organization (read 16 November 2026). ## Related terms - [Incident response plan](/glossary/incident-response-plan/) - [Incident response policy](/glossary/incident-response-policy/) - [Jump bag](/glossary/jump-bag/) - [Material cybersecurity incident](/glossary/material-cybersecurity-incident/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - cisa.gov: https://www.cisa.gov/topics/physical-security/insider-threat-mitigation (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/insider-threat/ --- # Jump bag, defined Glossary term, read 16 November 2026 **The short answer.** A jump bag is a kit of tools, checklists and contact lists that responders can grab at once when an incident is declared. The SANS Incident Handler's Handbook recommends keeping all the tools responders need in one. This entry was read on 16 November 2026 from the handbook, published 21 February 2012. ## What is a jump bag? A kit of tools, checklists and contact lists that responders can grab at once when an incident is declared. ## Definition A kit of tools, checklists and contact lists that responders can grab at once when an incident is declared. ## A sourced example The SANS Incident Handler's Handbook recommends keeping all the tools responders need "within a 'jump bag' that can be quickly grabbed by CIRT members during an incident" (SANS, 21 February 2012, read 16 November 2026). ## Related terms - [Incident response policy](/glossary/incident-response-policy/) - [Insider threat](/glossary/insider-threat/) - [Material cybersecurity incident](/glossary/material-cybersecurity-incident/) - [Playbook](/glossary/playbook/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - sans.org: https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/jump-bag/ --- # Material cybersecurity incident, defined Glossary term, read 16 November 2026 **The short answer.** A material cybersecurity incident is one a public company has determined to be material, and it must be reported on Form 8-K Item 1.05 within four business days of that determination. SEC release 33-11216 sets the rule. The materiality decision must be made without unreasonable delay. This entry was read on 16 November 2026. ## What is a material cybersecurity incident? A cybersecurity incident a public company has determined to be material. It must be reported on Form 8-K Item 1.05 within four business days of that determination. ## Definition A cybersecurity incident a public company has determined to be material. It must be reported on Form 8-K Item 1.05 within four business days of that determination. ## A sourced example SEC release 33-11216 states that an Item 1.05 Form 8-K "must be filed within four business days of determining an incident was material" (Federal Register, 4 August 2023, read 16 November 2026). ## Related terms - [Insider threat](/glossary/insider-threat/) - [Jump bag](/glossary/jump-bag/) - [Playbook](/glossary/playbook/) - [Procedure](/glossary/procedure/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - federalregister.gov: https://www.federalregister.gov/documents/2023/08/04/2023-16194/cybersecurity-risk-management-strategy-governance-and-incident-disclosure (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/material-cybersecurity-incident/ --- # Playbook, defined Glossary term, read 16 November 2026 **The short answer.** A playbook is a set of actionable steps for people to follow in one scenario, such as phishing. It is narrower than a plan and changes more often. NIST SP 800-61 Rev. 3 says playbooks provide actionable steps or tasks for various scenarios. This entry was read on 16 November 2026. ## What is a playbook? A set of actionable steps for people to follow in one scenario, such as phishing. It is narrower than a plan and changes more often. ## Definition A set of actionable steps for people to follow in one scenario, such as phishing. It is narrower than a plan and changes more often. ## A sourced example NIST SP 800-61 Rev. 3 says "Playbooks provide actionable steps or tasks for people to perform during various scenarios or situations" (read 16 November 2026). ## Related terms - [Jump bag](/glossary/jump-bag/) - [Material cybersecurity incident](/glossary/material-cybersecurity-incident/) - [Procedure](/glossary/procedure/) - [Recovery](/glossary/recovery/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/playbook/ --- # Procedure, defined Glossary term, read 16 November 2026 **The short answer.** A procedure is a documented description of how a technical or operating task is performed. Procedures are based on the policy and plan and can be tested. NIST SP 800-61 Rev. 3 says they should explain how technical processes are performed. This entry was read on 16 November 2026. ## What is a procedure? A documented description of how a technical or operating task is performed. Procedures are based on the policy and plan and can be tested. ## Definition A documented description of how a technical or operating task is performed. Procedures are based on the policy and plan and can be tested. ## A sourced example NIST SP 800-61 Rev. 3 says documented procedures "should explain how technical processes and other operating procedures should be performed" and can be tested or exercised periodically (read 16 November 2026). ## Related terms - [Material cybersecurity incident](/glossary/material-cybersecurity-incident/) - [Playbook](/glossary/playbook/) - [Recovery](/glossary/recovery/) - [Severity level](/glossary/severity-level/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/procedure/ --- # Recovery, defined Glossary term, read 16 November 2026 **The short answer.** Recovery is restoring affected systems and services to normal operation and confirming they work and are clean. NIST CSF 2.0 outcome RC.RP-05 says the integrity of restored assets is verified and normal operating status is confirmed. This entry was read on 16 November 2026 from NIST SP 800-61 Rev. 3. ## What is recovery? Restoring affected systems and services to normal operation and confirming they work and are clean. ## Definition Restoring affected systems and services to normal operation and confirming they work and are clean. ## A sourced example NIST CSF 2.0 outcome RC.RP-05 reads "The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmed" (read 16 November 2026). ## Related terms - [Playbook](/glossary/playbook/) - [Procedure](/glossary/procedure/) - [Severity level](/glossary/severity-level/) - [Significant incident (NIS2)](/glossary/significant-incident-nis2/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/recovery/ --- # Severity level, defined Glossary term, read 16 November 2026 **The short answer.** A severity level is a rating of an incident's impact on the organization that decides who is called and how fast. The SANS Incident Handler's Handbook gives an example scale of minor, moderate and high, based on organizational impact. This entry was read on 16 November 2026 from the handbook. ## What is a severity level? A rating of an incident's impact on the organization that decides who is called and how fast. ## Definition A rating of an incident's impact on the organization that decides who is called and how fast. ## A sourced example The SANS Incident Handler's Handbook gives an example: a single workstation being non-functional "can be considered minor, whereas a server being down could be considered a moderate impact", and stolen privileged data "as high" (read 16 November 2026). ## Related terms - [Procedure](/glossary/procedure/) - [Recovery](/glossary/recovery/) - [Significant incident (NIS2)](/glossary/significant-incident-nis2/) - [Triage](/glossary/triage/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - sans.org: https://www.sans.org/white-papers/33901/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/severity-level/ --- # Significant incident (NIS2), defined Glossary term, read 16 November 2026 **The short answer.** Under the EU NIS2 Directive a significant incident is one that has caused or can cause severe operational disruption or financial loss for the entity, or considerable damage to other people. Article 23(3) sets the test and Article 23(4) the reporting steps. This entry was read on 16 November 2026 from EUR-Lex. ## What is a significant incident under NIS2? Under the EU NIS2 Directive, an incident that has caused or can cause severe operational disruption or financial loss, or considerable damage to other people. ## Definition Under the EU NIS2 Directive, an incident that has caused or can cause severe operational disruption or financial loss, or considerable damage to other people. ## A sourced example NIS2 Article 23(3) defines it as an incident that "has caused or is capable of causing severe operational disruption of the services or financial loss for the entity concerned" or that has affected others by causing considerable damage (EUR-Lex, read 16 November 2026). ## Related terms - [Recovery](/glossary/recovery/) - [Severity level](/glossary/severity-level/) - [Triage](/glossary/triage/) - [Unsecured protected health information](/glossary/unsecured-phi/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - eur-lex.europa.eu: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/significant-incident-nis2/ --- # Triage, defined Glossary term, read 16 November 2026 **The short answer.** Triage is the first review of an incident report to confirm it is real and to decide how urgent it is. NIST CSF 2.0 outcome RS.MA-02 says incident reports are triaged and validated, and recommends a preliminary review of each new report. This entry was read on 16 November 2026. ## What is triage? The first review of an incident report to confirm it is real and to decide how urgent it is. ## Definition The first review of an incident report to confirm it is real and to decide how urgent it is. ## A sourced example NIST CSF 2.0 outcome RS.MA-02 reads "Incident reports are triaged and validated"; the recommendation is a preliminary review of a new report (read 16 November 2026). ## Related terms - [Severity level](/glossary/severity-level/) - [Significant incident (NIS2)](/glossary/significant-incident-nis2/) - [Unsecured protected health information](/glossary/unsecured-phi/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - nvlpubs.nist.gov: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-61r3.pdf (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/triage/ --- # Unsecured protected health information, defined Glossary term, read 16 November 2026 **The short answer.** Unsecured protected health information is information not rendered unusable, unreadable or indecipherable to unauthorized people by a method the HHS Secretary specifies. Only a breach of unsecured information triggers HIPAA breach notice, so encryption status matters. This entry was read on 16 November 2026 from 45 CFR 164.402. ## What is unsecured protected health information? Protected health information that has not been made unusable, unreadable or indecipherable to unauthorized people by a method the HHS Secretary specifies in guidance. Only a breach of unsecured information triggers HIPAA breach notice. ## Definition Protected health information that has not been made unusable, unreadable or indecipherable to unauthorized people by a method the HHS Secretary specifies in guidance. Only a breach of unsecured information triggers HIPAA breach notice. ## A sourced example 45 CFR 164.402 defines it as protected health information "that is not rendered unusable, unreadable, or indecipherable to unauthorized persons" through a technology or methodology specified by the Secretary (read 16 November 2026). ## Related terms - [Significant incident (NIS2)](/glossary/significant-incident-nis2/) - [Triage](/glossary/triage/) ## Related pages - [All incident response terms](/glossary/) - [Free incident response plan template](/) - [FAQ](/faq/) - [Incident response plan guide](/plans/) ## Sources - ecfr.gov: https://www.ecfr.gov/current/title-45/section-164.402 (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/glossary/unsecured-phi/ --- # 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/ --- # 3 dated items on incident response planning News, read 16 November 2026 **In short.** 3 dated items that change what an incident response plan should say, each from a primary source: NIST's new SP 800-61 Rev. 3, the ICO's 72-hour PECR period and the NCSC's reviewed supply chain guidance. Newest first, with read dates. ## What is new in incident response planning? 3 dated items are listed, newest first, each from a primary source. The newest is "NCSC reviews its supply chain security guidance". - [NCSC reviews its supply chain security guidance](/news/ncsc-supply-chain-guidance-reviewed/): 22 October 2025 - [ICO: PECR breach reports now due within 72 hours](/news/ico-pecr-breach-reports-72-hours/): 20 August 2025 - [NIST publishes SP 800-61 Rev. 3 on incident response](/news/nist-publishes-sp-800-61-rev-3/): 3 April 2025 ## Related pages - [Incident response plan guide](/plans/) - [Glossary](/glossary/) - [Standards map](/standards-map/) - [Data breach response plan](/data-breach/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/news/ --- # NCSC reviews its supply chain security guidance News, 22 October 2025 **The short answer.** The NCSC shows its supply chain security guidance as published on 28 January 2018 and reviewed on 22 October 2025, version 1.0. It sets out 12 principles and cites the 2025 Security Breaches Survey finding that very few UK businesses set minimum security standards for suppliers. Read on 16 November 2026. The guidance says most organizations rely on suppliers and that vulnerabilities can be inherent in, or introduced at, any point in the supply chain. It points to Cyber Essentials certification as a way to gain assurance about suppliers' basic technical controls. For incident planning, NIST SP 800-61 Rev. 3 outcome GV.SC-08 asks that relevant suppliers be included in incident planning, response and recovery. See the [third-party playbook](/playbooks/third-party-incident-response-playbook/) and the contact sheet in the [template](/). ## Related pages - [All dated items](/news/) - [Free incident response plan template](/) - [Incident response plan guide](/plans/) - [NIST publishes SP 800-61 Rev. 3 on incident response](/news/nist-publishes-sp-800-61-rev-3/) - [ICO: PECR breach reports now due within 72 hours](/news/ico-pecr-breach-reports-72-hours/) ## Sources - ncsc.gov.uk: https://www.ncsc.gov.uk/collection/supply-chain-security (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/news/ncsc-supply-chain-guidance-reviewed/ --- # ICO: PECR breach reports now due within 72 hours News, 20 August 2025 **The short answer.** The ICO says that from 20 August 2025 the Data Use and Access Act changes the reporting timescale for personal data breach reports under the Privacy and Electronic Communications Regulations from 24 hours to 72 hours after becoming aware. It matches the UK GDPR period. Read on 16 November 2026. The notice appears at the top of the ICO's Report a breach guide. It applies to communications service providers, which report under PECR on a separate form. The ICO guide also repeats the UK GDPR rule for other organizations: report a notifiable breach without undue delay and not later than 72 hours after becoming aware, with reasons if later, and provide information in phases where needed. Plans for UK organizations should show both routes. See the [UK template](/templates/incident-response-plan-template-uk/) and the [GDPR page](/data-breach/data-breach-response-plan-gdpr/). ## Related pages - [All dated items](/news/) - [Free incident response plan template](/) - [Incident response plan guide](/plans/) - [NCSC reviews its supply chain security guidance](/news/ncsc-supply-chain-guidance-reviewed/) - [NIST publishes SP 800-61 Rev. 3 on incident response](/news/nist-publishes-sp-800-61-rev-3/) ## Sources - ico.org.uk: https://ico.org.uk/for-organisations/report-a-breach/personal-data-breach/personal-data-breaches-a-guide/ (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/news/ico-pecr-breach-reports-72-hours/ --- # NIST publishes SP 800-61 Rev. 3 on incident response News, 3 April 2025 **The short answer.** NIST finalized SP 800-61 Revision 3, "Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile", on 3 April 2025. It supersedes Revision 2 of August 2012 and ties incident response to the six CSF 2.0 Functions instead of a separate circular life cycle. Read on 16 November 2026. The publication page records the draft of 3 April 2024 and the final of 3 April 2025. Authors listed are Alexander Nelson, Sanjay Rekhi, Murugiah Souppaya and Karen Scarfone. The page gives the publication date as April 2025. The abstract says the document helps organizations incorporate incident response recommendations and considerations throughout their cybersecurity risk management activities as described by CSF 2.0, so that they can prepare, reduce the number and impact of incidents, and improve detection, response and recovery. For template users the change matters in two ways. Plans can now be keyed to CSF outcomes such as RS.MA-03, and improvement is treated as continuous instead of a final step. See the [NIST layout template](/templates/incident-response-plan-template-nist/) and the [standards map](/standards-map/). ## Related pages - [All dated items](/news/) - [Free incident response plan template](/) - [Incident response plan guide](/plans/) - [ICO: PECR breach reports now due within 72 hours](/news/ico-pecr-breach-reports-72-hours/) - [NCSC reviews its supply chain security guidance](/news/ncsc-supply-chain-guidance-reviewed/) ## Sources - csrc.nist.gov: https://csrc.nist.gov/pubs/sp/800/61/r3/final (read 16 November 2026) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/news/nist-publishes-sp-800-61-rev-3/ --- # About Incident Response Plan Templates About, read 16 November 2026 **In short.** Incident Response Plan Templates publishes free incident response plan templates for people who have to write one: a general plan, plans for company types with their own legal rules, playbooks by incident type, and a data breach plan. Everything is in full on the page, and downloads as Word and PDF without sign-up. The site is written for the person who has been told to produce an incident response plan and does not know where to start, and for the security lead who wants a sourced starting point. Each template carries the rule or guidance it follows, with its source address and the date it was read. The publisher is the site itself. The two original assets are the template set and the standards map, both downloadable as CSV and JSON under CC BY 4.0. Firms that offer incident response planning are listed on the [services page](/services/) in alphabetical order with the same fields for each. Start with the [general template](/) or read [how the sources were used](/method/). ## Related pages - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact](/contact/) - [Privacy](/privacy/) - [Terms](/terms/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/about/ --- # How pages are written, sourced and corrected Editorial policy, read 16 November 2026 **In short.** Every fact on this site carries a source address and the date it was read. Legal and framework statements come from the regulator, the standards body or the agency that issued them. Where a source could not be read, the fact is left out and the gap is listed on the method page. Sources, in order of preference: the text of the rule or the standard; the issuing agency's guidance; a vendor's own published playbooks, labeled as the vendor's; and firms' own pages for what they say they offer. Templates are our own text. They follow the structure of the cited guidance, and each variant names the rule it adds. They are not legal advice, and counsel should confirm the notice rules for your situation. Firms are listed in alphabetical order with the same fields. No page gives a score or a verdict on any firm. See [corrections](/corrections/) to report an error and the [method page](/method/) for the full process. ## Related pages - [About](/about/) - [Corrections](/corrections/) - [Contact](/contact/) - [Privacy](/privacy/) - [Terms](/terms/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/editorial-policy/ --- # Corrections are made on the page and listed here Corrections, read 16 November 2026 **In short.** To correct a page, send its address, the statement you dispute and a source that shows the right fact. Corrections change facts only where a source supports the change, and each one is dated on this page. No corrections have been made to the edition of 16 November 2026. Send corrections to editor@incidentresponseplantemplates.com. Firms may correct facts about themselves under the same rule: send the page of your own site that states the fact. Law and guidance change. When a source changes, the affected pages are re-read and their review date is updated. See the [editorial policy](/editorial-policy/). ## Related pages - [About](/about/) - [Editorial policy](/editorial-policy/) - [Contact](/contact/) - [Privacy](/privacy/) - [Terms](/terms/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/corrections/ --- # Write to the editors Contact, read 16 November 2026 **In short.** The editors read every message sent to editor@incidentresponseplantemplates.com. For a correction, give the page address, the statement and a source. For a template request, say the company type or incident type and the rule that makes it distinct. There is no phone line and no advertising desk. Address: editor@incidentresponseplantemplates.com. Messages are used only to answer them and to make corrections. See the [privacy page](/privacy/) and the [corrections page](/corrections/). ## Related pages - [About](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Privacy](/privacy/) - [Terms](/terms/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/contact/ --- # This site sets no cookies and runs no analytics scripts Privacy, read 16 November 2026 **In short.** Incident Response Plan Templates sets no cookies and loads no analytics or advertising scripts. The host keeps standard request logs (address, time, page and user agent) for security and to count page views in total. The logs stay in the site's own storage and are not shared or sold. The downloads need no sign-up and no email address. Messages sent to the editors are used only to answer them and to make corrections. See the [terms](/terms/) and the [contact page](/contact/). ## Related pages - [About](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact](/contact/) - [Terms](/terms/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/privacy/ --- # Terms of use Terms, read 16 November 2026 **In short.** Text and datasets on this site may be copied, adapted and reused under CC BY 4.0 with a link to the page. Templates are starting points and are not legal advice. Facts are as published by their sources on the dates shown. Confirm every notice duty with counsel before relying on it. Names of agencies, standards and firms belong to their owners and are used to identify them. See the [editorial policy](/editorial-policy/) and the [privacy page](/privacy/). ## Related pages - [About](/about/) - [Editorial policy](/editorial-policy/) - [Corrections](/corrections/) - [Contact](/contact/) - [Privacy](/privacy/) - [Site method](/method/) - [Free incident response plan template](/) Last reviewed 16 November 2026. Canonical: https://incidentresponseplantemplates.com/terms/