The First 72 Hours of a Ransomware Claim: A Notification and Evidence Checklist
Most ransomware claims are won or lost before the forensics report arrives. This is an hour-by-hour checklist for the claim, with the main regulator deadlines by region in one table.
Hour 0 to 1: Call the Insurer's Hotline Before Anyone Else
When encrypted files or a ransom note appear, the order of your first calls largely decides which costs get reimbursed. Most cyber policies pay only if you give prompt notice and get prior consent before spending money. If you bring in your usual IT contractor, start restoring from backup or message the attacker before the insurer knows, you may pay for part of the response yourself. Every ransomware insurance claim process starts from that rule.
Give notice through the insurer's 24/7 incident hotline, or through the breach coach your policy names. Call your broker after that, not before. In most policy wordings, telling your broker doesn't count as formal notice to the insurer. The broker becomes useful once the claim is open.
- Have the policy number, the names of the insured entities and a named incident lead ready. Keep a printed or offline copy of the policy schedule, because ransomware often encrypts the shared drive it's saved on.
- Report the facts you have. Give the time you detected the attack, which systems are affected and whether there's a ransom note. Don't guess at the cause and don't admit liability.
- Record the claim reference, the time of the call and who you spoke to. That's the first entry in your evidence log.
- Ask: "Which costs are pre-approved now, and which need written consent?"
Notice requirements differ. Some policies say "as soon as practicable," and others set fixed windows, which can be measured in days or even hours for first-party cover. Read your wording before an incident and have your broker confirm how it's interpreted.
Hours 1 to 6: Panel Vendors, Breach Counsel and the Shortest Deadline
The insurer will usually connect you with a breach coach, typically a law firm. The coach then brings in forensics, restoration and, if needed, ransom negotiation firms from the insurer's panel. Panel vendors are already vetted and bill at agreed rates. Many policies cap off-panel vendors at panel rates, or won't cover them at all without consent in advance. So for most mid-size companies, the panel is the right default unless you've had an alternative pre-approved.
Typical 2026 market ranges, which vary by contract and region (confirm with vendors):
- Breach counsel: roughly $350 to $900 per hour in major markets, often lower in parts of Asia, Latin America and Africa.
- Digital forensics and incident response: roughly $250 to $550 per hour. A mid-market ransomware engagement commonly costs tens of thousands of dollars and can go well into six figures.
- Ransom negotiation: usually a flat fee or another arrangement set through the panel.
In the US, having counsel retain the forensics firm may help protect the report under legal privilege, though some courts have still ordered these reports disclosed. Privilege rules in the UK, the EU, India and elsewhere differ and are often less settled. Let counsel in each relevant jurisdiction decide how the engagement is structured.
Start the six-hour clock early. If you operate in India, CERT-In's 2022 directions require covered entities to report specified cyber incidents, ransomware included, within six hours of noticing them. Your local team should file the report while forensics is still scoping the attack. Waiting for the scoping to finish means you'll miss the deadline.
Forensic Evidence Preservation: What Not to Wipe
The urge to rebuild straight away is the biggest risk to forensic evidence preservation. Reimaging infected machines destroys the evidence of whether data was stolen. Whether data was stolen decides whether you have to notify regulators and customers.
- Isolate infected machines but leave them powered on. Disconnect them from the network so volatile memory can still be captured.
- Keep the ransom note, samples of encrypted files and any attacker contact details. Don't reply to the attacker unless the negotiator advises it.
- Export logs before they're overwritten. This includes firewall, VPN, EDR, DNS, domain controller and cloud audit logs. Some default SaaS and cloud logging tiers keep data for only days or weeks.
- Snapshot affected virtual machines and cloud workloads before anyone fixes them.
- Keep a chain-of-custody record showing who collected each item, when, how and where it's stored.
- Confirm backups are clean before restoring from them. Attackers may have been in the network for days or weeks before they encrypted anything.
Watch for an internal administrator "cleaning up" accounts or deleting suspicious files before forensics arrives. Freeze changes with a written instruction from the incident lead.
Breach Notification Deadlines by Region
Multinationals usually miss deadlines because each country team assumes someone else is tracking them. Put every applicable deadline on one tracker owned by counsel. The table lists common regimes but isn't complete. Sector rules in financial services, health and telecoms often add shorter deadlines.
| Regime | Who it covers | Deadline | When the clock starts |
|---|---|---|---|
| India CERT-In Directions (2022) | Service providers, intermediaries, data centres, body corporates and government organisations | 6 hours | Noticing the incident |
| EU NIS2 (as transposed nationally) | Essential and important entities | 24-hour early warning, 72-hour notification, final report within about one month | Becoming aware of a significant incident |
| EU GDPR / UK GDPR | Controllers processing personal data | 72 hours to the supervisory authority | Becoming aware of a personal data breach |
| Australia Cyber Security Act 2024 | Businesses above a turnover threshold that make a ransomware payment | 72 hours | Making the payment, or becoming aware it was made |
| Singapore PDPA | Organisations handling personal data | 3 calendar days to the PDPC | Assessing that the breach is notifiable (the assessment itself must be done promptly) |
| US SEC cyber disclosure rules | US-listed domestic registrants (Form 8-K Item 1.05). Foreign private issuers follow separate Form 6-K practice. | 4 business days | Determining the incident is material |
Other regimes to check include Brazil's ANPD rules (generally a short deadline counted in business days), India's DPDP Rules as their breach provisions phase in, the EU's DORA for financial entities, and US state and HIPAA requirements. Have licensed local counsel confirm which of these apply to you.
Cyber Claim Cost Tracking from the First Hour
Insurers don't pay costs you can't document. Set up cyber claim cost tracking on day one, with its own cost code in your finance system and a shared log. If you leave it until later, you'll be trying to rebuild the figures from old email threads months afterward.
- Vendor costs: each invoice should reference the claim number and the insurer's consent.
- Internal labor: overtime and contractor hours, logged daily by person and task. Many policies pay overtime but not ordinary salaries.
- Extra expense: temporary hardware, extra cloud capacity, manual workarounds and couriers.
- Business interruption: when systems went down, when they came back and which orders were lost. Keep 12 to 24 months of revenue and margin history to serve as the baseline.
Business interruption cover usually starts after a waiting period, often somewhere between 8 and 24 hours. Hypothetical example: a 200-person distributor is down for four days on a policy with a 12-hour waiting period. It can claim about 84 hours of lost net profit plus continuing expenses, less any retention. If it doesn't have timestamped downtime records, the amount becomes a negotiation.
Hours 24 to 72: Decisions That Need Written Consent
By the second day, the major decisions need written approval from the insurer. Get it before you do any of the following:
- Pay a ransom. You need insurer consent and sanctions screening against the relevant lists, including the US OFAC, UK OFSI, EU and UN lists. Paying a sanctioned group can be illegal whatever your policy says.
- Move from containment to a full rebuild, or change vendors.
- Issue public statements or notify customers. Counsel should review the wording first.
Claims usually run into trouble for four reasons: late notice, spending without consent, gaps in the evidence log, and staff in different countries telling different stories. Each of these can be fixed before an incident.
Do this week: put the hotline number, your policy's notice and consent clauses and the deadline table above on one page. Store it offline and give a copy to three named people, one each in finance, security and legal.
Questions buyers ask
Should we call our broker or the insurer first after a ransomware attack?
Call the insurer's incident hotline first, then tell your broker. Most policies define notice as notice to the insurer or its named breach coach, and a call to the broker may not count. Once the claim is open, your broker is valuable for advocacy and coverage questions.
Can we use our own IT or forensics firm instead of the insurer's panel?
Sometimes, but get the insurer's written agreement before the vendor starts work. Many policies cap off-panel vendors at panel rates or exclude them without advance consent. If you have a preferred firm, ask your broker to get it pre-approved at renewal, not during an incident.
Does the GDPR 72-hour deadline start when we discover the ransomware or when we confirm data was stolen?
It starts when you become aware of a personal data breach, which generally means you're reasonably certain personal data was affected. Regulators don't usually accept a long investigation as a reason to delay. You can notify in phases and send updates later. Counsel should record when you became aware and why.
Will our cyber policy reimburse a ransom payment?
Many cyber policies cover extortion payments, but only with the insurer's prior consent and only where paying is lawful, including after sanctions screening. Some countries now have ransom payment reporting rules. In Australia, for example, businesses above a turnover threshold must report payments within 72 hours. Check your extortion sublimit and any coinsurance with a licensed broker.
What records do insurers ask for when calculating business interruption losses?
Expect to provide 12 to 24 months of revenue and margin data, timestamped records of the outage and restoration, invoices for extra expenses and overtime logs. Some insurers appoint forensic accountants to check the figures. Records kept as the incident happens usually make settlement faster.
Written by the Auditvault Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.