# A ransomware playbook is a short, rehearsed set of steps for one scenario, kept where responders can find it

Definition, read 16 November 2026

**The short answer.** A ransomware playbook is a set of steps and decision points for a ransomware event, held by the people who will run the response. It is narrower than a response plan. NIST says its ransomware profile can be used when developing a countermeasure playbook. Microsoft Learn also lists ransomware incident response playbooks. Read on 16 November 2026.

## What is a ransomware playbook?

A ransomware playbook is an ordered procedure for a ransomware event, with decision points and owners. NIST says its ransomware profile can be used when developing a ransomware countermeasure playbook, which marks the playbook as something built from the profile's outcomes rather than a separate framework.

The plan says who has authority and what must be true. The playbook says what to do next and in what order. Both belong in the offline binder.

## How is a playbook different from a response plan?

| Feature | Response plan | Playbook |
| --- | --- | --- |
| Purpose | Authority, roles, duties, scope | Sequence of actions for one scenario |
| Length | Many sections, reviewed annually | A few pages; used live |
| Reader | Executives, counsel, IT | Responders on shift |
| Example here | [Plan template](/plan/ransomware-response-plan-template/) | [11-step playbook](/playbook/ransomware-playbook/) |

## What is the Microsoft ransomware playbook?

Microsoft Learn publishes a ransomware hub that lists "Microsoft ransomware incident response playbooks" and a page titled "Responding to ransomware attacks", alongside a question on how to download a ransomware incident response playbook. The hub is aimed at Microsoft environments.

Microsoft's separate incident response playbooks overview states the format of its playbooks: prerequisites, a workflow, a checklist and investigation steps. That four-part format is a useful template for any estate. Its listed playbooks cover phishing, password spray, app consent grant, compromised and malicious applications, and token theft. For non-Microsoft estates, use the steps in this site's playbook and map each to your own tools.

## Who should hold the playbook?

Give a printed copy to each role on the [roles page](/plan/ransomware-response-roles/), store one offline and keep one with the incident response firm. The #StopRansomware Guide asks that the plan be available as a hard copy and offline version; the same logic applies to the playbook.

## Related pages

- [Ransomware playbook: steps for the first 72 hours](/playbook/ransomware-playbook/)
- [Ransomware incident report template, ten sections](/playbook/ransomware-incident-report-template/)
- [Ransomware playbook flowchart: the decision paths](/playbook/ransomware-playbook-flowchart/)
- [Ransomware playbook keyed to NIST IR 8374 Rev. 1](/playbook/ransomware-playbook-nist/)
- [The ransomware readiness assessment](/assessment/)
- [The control mapping](/mapping/)

## Sources

- NIST IR 8374 Rev. 1, Ransomware Risk Management: A Cybersecurity Framework 2.0 Community Profile (CSRC record): https://csrc.nist.gov/pubs/ir/8374/r1/final (read 16 November 2026)
- Microsoft Learn: Microsoft defense against ransomware, extortion, and intrusion: https://learn.microsoft.com/en-us/security/ransomware/ (read 16 November 2026)
- Microsoft Learn: Incident response playbooks overview: https://learn.microsoft.com/en-us/security/zero-trust/security-operations-incident-response-playbooks (read 16 November 2026)
- 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)

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