# The steps of ransomware incident response are six, and the first three must run in sequence

Steps, read 16 November 2026

**The short answer.** The steps of ransomware incident response are: detect and analyze, report and notify, contain, eradicate, recover and review. The #StopRansomware Guide says to move through its first three checklist steps in sequence. Each step below has an owner and a done-when test so progress can be reported without guessing. Read on 16 November 2026.

## What are the steps of ransomware incident response?

Six steps cover the guide's four phases. The table shows what each aims at, who owns it and how you know it is done. The [11-step playbook](/playbook/ransomware-playbook/) gives the finer sequence.

| Step | Goal | Owner | Done when |
| --- | --- | --- | --- |
| 1 Detect and analyze | Know which systems are affected; isolate; triage for restoration; examine logs | Technical lead | Affected systems isolated and listed; initial understanding documented |
| 2 Report and notify | Get help and meet duties | Incident commander and counsel | Management, insurer, providers and law enforcement told; clocks started |
| 3 Contain | Stop the spread and cut access routes | Technical lead and identity lead | Access routes disabled; evidence imaged and preserved |
| 4 Eradicate | Remove the attacker and persistence | Security lead | Persistence reviewed; systems rebuilt from clean images; passwords reset |
| 5 Recover | Restore business services | Backup and recovery lead | Critical services restored from verified backups, without reinfection |
| 6 Review | Fix the causes | Executive decider | Lessons-learned review held; plan and controls updated |

Steps follow the guide's four phases. Owners are suggestions; set yours in the plan template.

## What are incident response steps for a ransomware attack when you are the person on call?

Do these three first and in this order, as the guide says: determine which systems are affected and isolate them; triage the affected systems for restoration; examine the detection systems and logs. If you cannot disconnect a system, power it down to stop spread, accepting that this loses volatile memory evidence.

Then call the executive decider, using a phone. The [first hour page](/decisions/first-hour-of-ransomware/) lists the questions to ask in that call.

## What is the ransomware incident response process, and who hands off to whom?

The process hands off at three points: from the on-call responder to the executive decider (authority), from the decider to counsel and the insurer (obligations), and from the technical lead to the backup lead (recovery). Each handoff needs a named person on both sides. See [roles](/plan/ransomware-response-roles/).

## Related pages

- [Ransomware incident response: the whole process explained](/response/ransomware-incident-response/)
- [Ransomware incident response procedure and techniques](/response/ransomware-incident-response-procedure/)
- [Ransomware first 24 hours: an hour-by-hour guide](/response/first-24-hours/)
- [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)
- CISA: Cybersecurity Performance Goals 2.0 (CPG 2.0) goal list: https://www.cisa.gov/cybersecurity-performance-goals-2-0-cpg-2-0 (read 16 November 2026)

Last reviewed 16 November 2026. Canonical: https://ransomwarereadinessassessment.com/response/ransomware-incident-response-steps/
