Skip to content
Ransomware Readiness Assessment

Playbook, stepsChecked

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

01

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.

  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.
02

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.

StepTrigger or inputAction takenOwnerTime doneEvidence reference
1 Declare[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
2 Isolate[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
3 Out-of-band coordination[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
4 Triage[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
5 Examine and hunt[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
6 Notify[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
7 Preserve[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
8 Data theft and clocks[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
9 Payment path[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
10 Eradicate and rebuild[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
11 Restore and close[ ][ ][ ][ ][ ]Fill in on the printed copy: Trigger or input, Action taken, Owner, Time done, Evidence reference.
03

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. For the function-by-function version keyed to NIST, see the NIST playbook page.

Sources

Read 16 November 2026, the day this page was last reviewed, unless a line shows another date.

  1. CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026)
  2. OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021
  3. NIST IR 8374r1, full text (June 2026)

Last reviewed 16 November 2026.