Incident response plan template

Fill in your team, contacts, severity levels and the steps for each phase of incident response, following NIST guidance. The example text shows what each section should say. Download or print the finished plan.

Free, no sign-upUpdated

Northwind Health
Incident Response Plan

1. Purpose and scope
This plan sets out how we prepare for, detect, respond to and recover from information security incidents affecting our systems, our customers' data and our employees' data. It applies to all employees, contractors and systems we operate or rent.

2. Incident response team and roles
Incident lead: [name], deputy [name]. Technical lead: [name]. Communications lead: [name]. Legal and privacy: [name or outside counsel]. Executive sponsor: [CEO or CTO].

3. Contacts
On-call: [phone or paging tool]. Cyber insurance hotline: [number, policy number]. Outside counsel: [firm, contact]. Forensics retainer: [firm, contact]. Cloud provider support: [plan and link].

4. Severity levels
SEV 1, critical: confirmed breach of customer data or a full outage. Respond immediately, executive sponsor informed within 1 hour.
SEV 2, high: suspected breach or partial outage. Respond within 4 hours.
SEV 3, medium: contained malware, a lost encrypted laptop. Respond within 1 business day.
SEV 4, low: policy violations, phishing reported and blocked. Respond within 3 business days.

5. Preparation
Centralized logging kept for 12 months. Daily encrypted backups tested each quarter. Endpoint protection on all devices. Annual tabletop exercise and security awareness training for all staff.

6. Detection and analysis
Anyone who suspects an incident reports it at [channel or email]. The on-call engineer confirms, assigns a severity and opens an incident record with a timeline. Evidence is preserved before changes are made.

7. Containment, eradication and recovery
Isolate affected systems and revoke compromised credentials. Remove the cause, patch the weakness and restore from known-good backups. Monitor closely for recurrence before declaring recovery.

8. Communication and notification
The communications lead drafts all statements; legal approves them. Notify customers and regulators as required by law and contract, for example within 72 hours to the supervisory authority under GDPR where it applies, and within 60 days to affected individuals under HIPAA.

9. Post-incident review
Within 10 business days of closing a SEV 1 or SEV 2 incident, hold a blameless review. Record the root cause, what worked, what did not and the actions, each with an owner and a date.

10. Plan maintenance and testing
The security lead owns this plan. It is reviewed every year and after every SEV 1 incident, and tested with at least one tabletop exercise a year.

The incident response life cycle

  1. 01Prepare

    Roles, contacts, logging, backups and practice before anything happens.

  2. 02Detect and analyze

    Spot the incident, confirm it, rate its severity and record a timeline.

  3. 03Contain, eradicate, recover

    Stop the damage, remove the cause and restore service safely.

  4. 04Learn

    Review what happened and fix the weaknesses that allowed it.

Common notification deadlines

RuleDeadline
GDPR (EU and UK)Notify the supervisory authority within 72 hours of becoming aware of a personal data breach, where it is likely to result in a risk to people.
HIPAA Breach Notification RuleNotify affected individuals without unreasonable delay and no later than 60 days after discovery.
US state breach lawsEvery state has its own law and deadline; many require notice to residents and some to the state attorney general.
Customer contractsCheck your contracts and data processing agreements; many set their own notification window.

This table is a summary, not legal advice. Confirm the rules that apply to you with counsel.

Keep the plan and the evidence together

Evidr writes an incident response policy for your company, collects it with the rest of your audit evidence and records who signed it, so the plan, its reviews and its tests are ready for SOC 2, ISO 27001 or HIPAA auditors.

Questions people ask

Anything we have not answered here, ask us directly.

Contact us
What should an incident response plan include?

Scope, roles and contacts, severity levels, and the steps for preparation, detection and analysis, containment, eradication and recovery, communication and notification, and post-incident review, plus how the plan is tested and kept up to date.

What are the phases of incident response?

The widely used phases come from NIST SP 800-61 Revision 2: preparation; detection and analysis; containment, eradication and recovery; and post-incident activity. NIST replaced it in April 2025 with Revision 3, which organizes incident response around the six functions of the Cybersecurity Framework 2.0: govern, identify, protect, detect, respond and recover.

Who should be on the incident response team?

An incident lead, a technical lead, someone for communications, legal or privacy support and an executive sponsor who can make business decisions. Small companies often combine roles, but each role still needs a named person and a deputy.

How often should an incident response plan be tested?

At least once a year with a tabletop exercise, and after any major incident or significant change to your systems or team. SOC 2 and ISO 27001 auditors usually ask for evidence of testing.

Do SOC 2, ISO 27001 and HIPAA require an incident response plan?

All three expect documented incident response procedures. The HIPAA Security Rule requires security incident procedures, ISO 27001 Annex A includes incident management controls, and SOC 2 includes criteria on responding to security incidents.