# A ransomware playbook is a decision sequence you follow in order, with a named owner for each step

Playbook, steps, read 16 November 2026

**The short answer.** A ransomware playbook is a short ordered set of steps with owners and decision points, used under pressure. This one has 11 steps for the first 72 hours, drawn from the #StopRansomware Guide checklist and NIST IR 8374 Rev. 1. The CISA guide says to move through its first three steps in sequence. Read on 16 November 2026.

## What are the steps in a ransomware playbook?

The 11 steps below follow the guide's order. Times are targets to set, not published standards. The owner column uses the roles on the [roles page](/plan/ransomware-response-roles/).

1. **Declare the incident and open the decision log.** The incident commander declares the incident under the plan triggers and starts the time-stamped log. Target: first 15 minutes. Owner: Incident commander. Source: Plan template sections 5 and 6.
2. **Determine impacted systems and isolate them.** If several systems or subnets look affected, take the network offline at the switch level; unplug or remove from Wi-Fi if that is not possible; snapshot cloud volumes. Prioritize critical systems. Owner: Technical lead. Source: #StopRansomware Guide, Detection and Analysis.
3. **Coordinate by phone, not network channels.** Use out-of-band communication such as phone calls so the actor does not learn that mitigation is under way and move laterally faster. Owner: Incident commander. Source: #StopRansomware Guide, Detection and Analysis.
4. **Triage systems for restoration.** Mark systems for restoration from the predefined critical asset list covering health and safety, revenue and other critical services, and note systems not affected so they can wait. Owner: Technical lead and business owners. Source: #StopRansomware Guide, Detection and Analysis.
5. **Examine logs and detection tools; start hunting.** Check for new privileged accounts, anomalous VPN logins, backup and shadow copy tampering, remote management tools, credential dumping and signs of data leaving the network. Owner: Security lead. Source: #StopRansomware Guide, threat hunting list.
6. **Notify counsel, insurer, incident response firm and law enforcement.** Report to CISA, the local FBI field office, the FBI Internet Crime Complaint Center or the Secret Service. Share information so help can start. Owner: Incident commander and counsel. Source: #StopRansomware Guide, Reporting and Notification.
7. **Preserve evidence.** Image and capture memory of a sample of devices; keep logs, ransom notes and malware samples. Preserve volatile data first. Owner: Technical lead. Source: #StopRansomware Guide, Containment and Eradication.
8. **Decide whether data was taken, and start the reporting clocks.** Counsel works through the clock table: Form 8-K Item 1.05, HIPAA, state law, contracts. Ask law enforcement about possible decryptors. Owner: Breach counsel. Source: Plan template section 9.
9. **If an extortion demand exists, follow the payment decision path.** No contact with the actor except by the named decider. Screen for sanctions, consult counsel, insurer and law enforcement, and log reasons. Owner: Executive decider. Source: OFAC advisory of 21 September 2021.
10. **Eradicate, rebuild identity first and reset credentials.** Identify involved accounts and systems, remove persistence, rebuild by priority from standard images, then reset passwords once the environment is clean. Owner: Identity lead and technical lead. Source: #StopRansomware Guide, Containment and Eradication.
11. **Restore, verify and close.** Restore from offline, encrypted backups in priority order; verify integrity; add only clean systems to any recovery network; the designated authority declares the incident over; hold lessons learned. Owner: Backup and recovery lead. Source: #StopRansomware Guide, Recovery and Post Incident Activity.

## Is there a ransomware playbook template?

Yes. Copy the table below. It is the blank form of the steps above, with a column for the time each step finished and for the evidence.

| Step | Trigger or input | Action taken | Owner | Time done | Evidence reference |
| --- | --- | --- | --- | --- | --- |
| 1 Declare | [ ] | [ ] | [ ] | [ ] | [ ] |
| 2 Isolate | [ ] | [ ] | [ ] | [ ] | [ ] |
| 3 Out-of-band coordination | [ ] | [ ] | [ ] | [ ] | [ ] |
| 4 Triage | [ ] | [ ] | [ ] | [ ] | [ ] |
| 5 Examine and hunt | [ ] | [ ] | [ ] | [ ] | [ ] |
| 6 Notify | [ ] | [ ] | [ ] | [ ] | [ ] |
| 7 Preserve | [ ] | [ ] | [ ] | [ ] | [ ] |
| 8 Data theft and clocks | [ ] | [ ] | [ ] | [ ] | [ ] |
| 9 Payment path | [ ] | [ ] | [ ] | [ ] | [ ] |
| 10 Eradicate and rebuild | [ ] | [ ] | [ ] | [ ] | [ ] |
| 11 Restore and close | [ ] | [ ] | [ ] | [ ] | [ ] |

## Is there a ransomware playbook example?

The numbered steps above are a worked example. For the decision paths drawn as a flowchart, see the [flowchart page](/playbook/ransomware-playbook-flowchart/). For the function-by-function version keyed to NIST, see the [NIST playbook page](/playbook/ransomware-playbook-nist/).

## Related pages

- [Ransomware playbook keyed to NIST IR 8374 Rev. 1](/playbook/ransomware-playbook-nist/)
- [Ransomware incident report template, ten sections](/playbook/ransomware-incident-report-template/)
- [What is a ransomware playbook, and who holds it?](/playbook/what-is-a-ransomware-playbook/)
- [Ransomware playbook flowchart: the decision paths](/playbook/ransomware-playbook-flowchart/)
- [The ransomware readiness assessment](/assessment/)
- [The control mapping](/mapping/)

## Sources

- CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026): https://www.cisa.gov/stopransomware/ransomware-guide (read 16 November 2026)
- OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021: https://ofac.treasury.gov/media/912981/download?inline (read 16 November 2026)
- NIST IR 8374r1, full text (June 2026): https://nvlpubs.nist.gov/nistpubs/ir/2026/NIST.IR.8374r1.pdf (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://ransomwarereadinessassessment.com/playbook/ransomware-playbook/
