FlowchartChecked
A ransomware playbook flowchart shows eight decisions, each with a yes path and a no path
01
What does a ransomware playbook flowchart look like?
Read the table row by row. Each row is a decision node, and the yes and no columns name the next node or action. Node numbers match the playbook steps.
| Node | Question | If yes | If no | Source |
|---|---|---|---|---|
| A | Are systems showing encryption, a ransom note or backup tampering? | Go to B | Keep monitoring; go to E if data theft is suspected | Guide: threat hunting list |
| B | Can affected systems be disconnected individually? | Disconnect them; go to C | Take the network offline at the switch level; if even that is not possible, power down and accept that volatile memory is lost | Guide: Detection and Analysis |
| C | Has the actor tried to deliver or demand anything? | Go to F | Go to D | Guide; IC3 |
| D | Is there evidence that data left the network? | Go to E | Continue to G | Guide: threat hunting list |
| E | Do personal, health or regulated data or a material event apply? | Start the reporting clocks with counsel; go to F or G | Record why not and keep reviewing | SEC final rule; 45 CFR 164 |
| F | Has law enforcement been contacted, counsel and insurer consulted, and sanctions screening done? | Decider records a decision; go to G | Stop contact with the actor until done | OFAC advisory of 21 September 2021 |
| G | Are backups verified as clean and out of the attacker's reach? | Restore in priority order; scan before reconnecting | Rebuild from golden images; check for dropper malware before restoring | Guide: Recovery; NIST RC.RP-03 |
| H | Is the identity layer trusted? | Reset credentials once clean; reconnect in stages | Rebuild directory services first and reset all passwords after the environment is clean | Guide: Containment and Eradication |
02
Why write the flowchart as a table?
A table prints on one page, reads with a screen reader and survives a failed projector. The first three steps of the guide must run in sequence, and the table enforces order by node letter.
Related pages
Sources
Read 16 November 2026, the day this page was last reviewed, unless a line shows another date.
- CISA, MS-ISAC, FBI and NSA: #StopRansomware Guide (September 2023 edition, page read 16 November 2026)
- OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021
- FBI Internet Crime Complaint Center: Ransomware
- Federal Register: SEC final rule on cybersecurity risk management, strategy, governance and incident reporting (4 August 2023)
- eCFR: 45 CFR 164.404, notification to individuals
- NIST IR 8374r1, full text (June 2026)
Last reviewed 16 November 2026.