Skip to content
Ransomware Readiness Assessment

Guide, stepsChecked

The first 24 hours of a ransomware attack go in four blocks: the first hour, hours one to four, four to eight and eight to twenty-four

01

What should you do in the first 24 hours of a ransomware attack?

Follow the order, not the clock. The #StopRansomware Guide asks responders to move through its first three steps in sequence, and the time blocks below hang the rest of the checklist around them.

  1. Hour 0 to 1: isolate and call. Isolate affected systems; if several subnets are affected take the network offline at the switch level. Use out-of-band communication. Call the executive decider. Open the decision log. Owner: On-call responder. Source: Guide, Detection and Analysis.
  2. Hours 1 to 4: preserve and bring in help. Image a sample of devices and capture memory; keep logs and ransom notes. Notify the insurer, breach counsel, and the incident response firm. Report to CISA, the local FBI field office, IC3 or the Secret Service. Owner: Technical lead and incident commander. Source: Guide, Reporting and Notification; Containment and Eradication.
  3. Hours 4 to 8: scope and decide. Hunt for the entry route, dropper malware, new accounts, backup tampering and data leaving the network. Counsel starts the reporting clocks. No contact with the actor except by the decider. Owner: Security lead and counsel. Source: Guide, threat hunting list; OFAC advisory.
  4. Hours 8 to 24: protect backups and plan recovery. Confirm backups are intact and offline. Rank systems for restoration from the critical asset list. Rebuild identity first when it is affected. Agree an update rhythm with leadership. Owner: Backup and recovery lead. Source: Guide, Recovery and Post Incident Activity.
02

What goes in a ransomware incident response checklist?

Print the list below. Each line comes from the guide's Part 2 checklist.

  • Affected systems identified and isolated, in a coordinated way.
  • Out-of-band channel in use; attacker not tipped off.
  • Critical systems prioritized for restoration; unaffected systems noted.
  • Logs and detection tools examined for precursor malware and data theft.
  • Management, insurer and providers informed.
  • CISA, FBI field office, IC3 or Secret Service contacted.
  • System images and memory captured from a sample of devices.
  • Possible decryptors asked about through federal law enforcement.
  • Access routes cut: VPN, remote access, single sign-on if needed.
  • Persistence searched for, outside in and inside out.
  • Rebuild plan agreed, in priority order, from standard images.
  • Backups protected and verified; recovery network kept clean.
03

What if you only have an hour?

Do the first block and the call. The first hour page explains the isolate-or-shut-down choice, and the playbook takes the sequence to 72 hours.

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. OFAC: Updated Advisory on Potential Sanctions Risks for Facilitating Ransomware Payments, 21 September 2021
  3. FBI Internet Crime Complaint Center: Ransomware

Last reviewed 16 November 2026.