PlaybookChecked 16 November 2026
Malware incident response playbook
Stages
The template in full
1 When to use this playbook
Use this playbook when endpoint protection or a user reports malicious software on one or more devices. It excludes extortion cases, which are covered elsewhere.
2 Before you start: prerequisites
Complete these before an incident, as part of planning.
- Endpoint detection and response or antivirus alerts reach a monitored place.
- Offline, tested backups exist for important data.
- Responders can isolate a device remotely.
- A clean rebuild image exists for each standard device.
3 Workflow
Work in this order. Record each step and its time in the incident log.
- Validate the alert and identify the device, user and malware family if known.
- Short-term containment: isolate the device from the network. Do not power it off if memory evidence may be needed.
- Check for spread: other devices with the same file, shared drives, and accounts used on the device.
- Reset passwords and revoke sessions for any account that was used on the infected device.
- Take a backup image of the affected system before wiping it.
- Eradicate: reimage from a trusted source, replace compromised files with clean versions, and patch what was exploited.
- Recover: restore data from a verified backup onto the clean system, and watch it for signs of re-infection.
4 Decision points
Stop at each of these and record the decision, the decider and the time.
| Decision | Who decides | Information needed |
|---|---|---|
| Is this a single device or a spread? | Technical lead | Alerts, file hashes, network connections |
| Rebuild or clean in place? | Technical lead | Malware type, risk of rootkits, time to rebuild |
| Is data stolen? | Technical lead, privacy lead | Outbound traffic, staging files, cloud sync |
5 Notices to check
Open section 10 of the plan and confirm whether any of these start a notice clock.
- If data left the network, assess it under the data breach plan.
- If the malware reached systems that run a service for customers, check customer contract notice terms.
6 Exit criteria and follow-up
Close the playbook only when all of these are true.
- Malware removed from every device or the device rebuilt.
- Credentials reset.
- No new alerts for [period].
- The infection route is found and closed.
About this playbook
What is the incident response playbook for malware?
The NCSC says malware can cause harm in many ways: locking devices, stealing, deleting or encrypting data, taking control of devices, obtaining credentials and mining cryptocurrency. It stresses always having a recent offline backup of important data.
CISA's eradication list includes reimaging affected systems from gold sources, rebuilding hardware where rootkits are involved, replacing compromised files with clean versions, installing patches and resetting passwords on compromised accounts. Ransomware extortion decisions are covered by other specialist guidance and not here.
Download the template
Free, no sign-up. Word (.docx, 3 KB): download. PDF (46 KB): download. Both files carry the same text as this page, edition 16 November 2026.
Related pages
- Incident response playbook: what it is and how to build a library
- Free incident response plan template
- Incident response playbook for phishing
- Business email compromise incident response playbook
- Insider threat incident response playbook
- Lost or stolen device incident response playbook
- Incident response plan templates: the full set
- Incident response steps: the order and who does what
Sources
- NCSC, Mitigating malware and ransomware attacks
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
- SANS Institute, Incident Handler's Handbook (21 February 2012)
Last reviewed 16 November 2026. Each source above was read that day.