Skip to content
Ransomware Readiness Assessment

StepsChecked

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

01

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 gives the finer sequence.

Steps follow the guide's four phases. Owners are suggestions; set yours in the plan template.
StepGoalOwnerDone when
1 Detect and analyzeKnow which systems are affected; isolate; triage for restoration; examine logsTechnical leadAffected systems isolated and listed; initial understanding documented
2 Report and notifyGet help and meet dutiesIncident commander and counselManagement, insurer, providers and law enforcement told; clocks started
3 ContainStop the spread and cut access routesTechnical lead and identity leadAccess routes disabled; evidence imaged and preserved
4 EradicateRemove the attacker and persistenceSecurity leadPersistence reviewed; systems rebuilt from clean images; passwords reset
5 RecoverRestore business servicesBackup and recovery leadCritical services restored from verified backups, without reinfection
6 ReviewFix the causesExecutive deciderLessons-learned review held; plan and controls updated
02

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 lists the questions to ask in that call.

03

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.

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. CISA: Cybersecurity Performance Goals 2.0 (CPG 2.0) goal list

Last reviewed 16 November 2026.