Why the first 72 hours matter
Ransomware and business email compromise account for well over half of all SME cyber claims, and the NetDiligence SME average of roughly $246,000 per incident spikes sharply when business interruption occurs. Complex ransomware engagements routinely consume 150–300+ forensic hours; at emergency rates of $750–$1,500+ per hour, that alone can reach $100,000–$300,000+. Most of what drives that number is decided before day four.

Hours 0–4: contain without destroying evidence
- Isolate, don't wipe. Disconnect affected hosts and segments from the network. Avoid reimaging, rebuilding or powering down systems until forensic imaging decisions are made — memory and logs disappear.
- Protect backups. Take backup systems offline or confirm immutability; threat actors target them first.
- Move communications out of band. Assume email, chat and collaboration tools on the compromised domain are monitored. Set up a separate channel and a phone tree for the response team.
- Reset privileged credentials carefully. Coordinate identity resets with responders so you don't tip off an attacker still in the environment or lock out the response team.
- Start a timeline. Record when the incident was detected and by whom; these dates start legal clocks.
Hours 4–24: counsel, insurer and forensics
- Notify your cyber insurer through the claims hotline. Panel requirements decide who you may hire.
- Engage breach counsel to establish privilege and direct the investigation (see breach counsel & privilege).
- Retain DFIR through counsel. With a retainer in place this takes minutes; without one, expect contracting delays and emergency rates.
- Preserve the ransom note and any attacker contact details. Do not engage the threat actor without counsel and an experienced negotiator.
- Consider law enforcement contact through counsel.
Hours 24–72: scope and decide
Forensics works to answer three questions: how the attacker got in, whether they are still present, and whether data was exfiltrated before encryption. Double-extortion groups steal data first, so restoring from backups does not end the incident — exfiltration triggers state breach notification analysis and, potentially, 30-day consumer clocks in California, New York, Florida, Washington, Colorado and Maine.
In parallel, the organization evaluates recovery options: restore from clean backups, rebuild, or consider whether payment is being contemplated at all. Threat-actor intelligence — what this group typically does, whether its decryptors work, whether it honors deletion claims — informs that decision far more than the ransom demand itself.
Ransom payment reality and OFAC sanctions screening
- Payment does not guarantee recovery. Decryptors can be slow or partial, and data deletion promises are unverifiable.
- Sanctions exposure. Paying a threat actor linked to a sanctioned person or jurisdiction can violate U.S. sanctions administered by the Treasury Department's Office of Foreign Assets Control (OFAC). Sanctions screening and documented diligence by experienced counsel and negotiators are prerequisites to any payment discussion.
- Insurance consent. Most policies require carrier consent before any extortion payment.
- Documentation. NYDFS-regulated entities must later justify any payment in writing, including alternatives considered and sanctions diligence.
Ransom payment reporting clocks
| Framework | Trigger | Deadline | Notes |
|---|---|---|---|
| NYDFS Part 500 23 NYCRR § 500.17 | Cybersecurity event determination | 72 hours | NY-licensed financial entities |
| NYDFS Part 500 | Extortion payment made | 24 hours | Written justification within 30 days |
| CIRCIA (CISA) 6 U.S.C. § 681b | Reasonable belief of covered incident | 72 hours | Pending CISA final rule effective date |
| CIRCIA (CISA) | Ransom payment made | 24 hours | Pending CISA final rule effective date |
| SEC Item 1.05 | Materiality determination | 4 business days | Public companies |
| GDPR Art. 33 | Awareness of personal data breach | 72 hours | EU personal data |
Toggle Ransom paid in the Deadline Tracker to add the 24-hour clocks to your schedule.
Why downtime multiplies cost
Business interruption is what turns a manageable claim into a severe one. Every day systems stay down adds lost revenue, overtime, extra forensic and recovery hours, and customer attrition. Recovery speed depends on things decided long before the attack: backup integrity and isolation, a tested restoration order, and a forensic firm already under contract. NetDiligence data shows crisis services alone now represent about 47% of SME incident cost — before counting lost income.
Preparing before it happens
- Retainer or warm MSA. Lock in $300–$600/hr instead of $750–$1,500+/hr. Compare models on the retainer guide.
- Breach counsel identified. Know who you will call, and confirm with your insurer they are approved.
- Ransomware tabletop exercise. $7,500–$25,000 to rehearse payment governance, out-of-band communications and the 24-hour reporting decisions.
- Offline, tested backups. Restoration you have actually practiced.
- Budget the worst case. Use the Budget Modeler with the ransomware scope selected to see the retainer-versus-emergency delta.
Facing an incident now, or arranging readiness? Coordinate response — send scope only, never personal data or logs.