Breach Risk Direct.
Claims & Coverage

Eight Consent Mistakes That Leave Your Incident Response Bills Uninsured

Your policy covers forensics, but the insurer may still dispute the invoice. Here are eight consent mistakes that turn covered incident response costs into contested bills, and what to do instead.

Breach Risk Direct editorial team · November 2026 · 10 min read

Your cyber policy schedule probably lists forensics, breach counsel, notification, crisis communications and extortion as covered. Whether the insurer pays a given invoice is a separate question, and it usually turns on a condition most buyers read once at binding and forget: costs must be incurred with the insurer's prior written consent.

Cyber insurance consent for incident response costs is the step that turns coverage on paper into a claim that gets paid. Lloyd's market wordings, large carrier forms in North America and Europe, and MGA products sold across Asia-Pacific and the Middle East phrase it differently, but the core language is similar. Typical (illustrative) formulations include:

  • "The Insurer shall not be liable for any Costs incurred without its prior written consent, such consent not to be unreasonably withheld."
  • "Costs must be reasonable and necessary and incurred with a Panel Provider or another provider agreed in writing by the Insurer."
  • "Emergency Costs incurred within [48/72] hours of discovery are covered without prior consent, provided a Panel Provider is used."

That last carve-out matters more than most buyers realize. Many policies give a short consent-free window, but only if you use the insurer's panel, and some cap the emergency spend. Miss the window or step outside the panel and the insurer rarely denies the whole claim. It typically pays what it would have paid had you followed the process, and you cover the difference.

Advertisement

Hypothetical example: say a 120-person logistics company runs up USD 310,000 in response bills after a ransomware event. The insurer accepts the claim but disputes USD 95,000: an off-panel forensics firm billing above panel rates, two weeks of managed service provider (MSP) overtime nobody approved, and a PR retainer signed before the insurer was notified. Every line item was "covered." None had consent. The eight mistakes below are the usual sources of disputes like this, each with the wording to check and what to do instead.

Mistakes one and two: calling the forensics firm and lawyer you already know

Mistake one: hiring an off-panel forensics firm on day one

Under pressure, teams call the firm their CISO trusts or their security vendor recommends. If it isn't on the panel, you depend on what the policy says about non-panel providers. Wordings fall into three broad groups:

  • Panel-only: off-panel costs are excluded, or covered only if the insurer agrees in writing beforehand.
  • Panel rates apply: off-panel firms are allowed with consent, but reimbursement is capped at what the panel firm would have charged.
  • Open choice: any reasonable provider is allowed, usually still subject to consent and a "reasonable and necessary" test. This is more common in large-company and bespoke programs.

What to do instead: if you have a preferred firm, get it approved before you need it. Ask your broker at renewal for a named-provider endorsement listing your pre-approved vendors and agreed rates. Insurers often grant these, especially when the firm already sits on another carrier's panel. If you missed renewal, request a mid-term letter of approval. A short email from claims or underwriting confirming the vendor beats arguing about it afterward.

Mistake two: letting your regular law firm act as breach counsel

Your general counsel's usual firm may be excellent at contracts and still be the wrong choice here. Panel breach counsel, sometimes called the breach coach, typically coordinates the other vendors, runs notification analysis across jurisdictions, and works under pre-negotiated rates. An outside firm billing at standard partner rates is a classic source of reduced reimbursement.

Privilege adds a second wrinkle. The US practice of having counsel engage forensics to protect the report doesn't carry over cleanly to many civil law countries, and common law jurisdictions treat it differently too. What to do instead: if you want your own firm, get consent for it as monitoring counsel alongside panel counsel, or get its rates approved in writing. Ask a licensed lawyer in each key jurisdiction how privilege works for forensic reports there.

Mistakes three and four: signing engagement letters and spending before you notify

Mistake three: accepting rates and scope nobody approved

Vendors arrive with engagement letters that often include open-ended scope, emergency surcharges, minimum retainers and travel at cost. Signing one doesn't bind your insurer. Panel firms usually work to pre-negotiated rate cards, and adjusters measure every invoice against them. The gap can be wide.

Cost lineTypical panel rate (USD/hour)Typical off-panel rate (USD/hour)Consent point to check
Digital forensics and IR250-450400-750Rate cap, scope, estimated hours
Breach counsel350-650700-1,500+Named firm, blended rate
Crisis communications/PR200-400300-700Crisis sublimit, retainer terms
Ransom negotiationOften flat fee or cappedVaries widelyExtortion consent, sanctions screening

These are indicative 2026 market ranges. They vary by region, insurer, incident size and contract, so confirm current rates with your broker and the vendors. Rates in Western Europe and Australia often sit near US levels. Parts of Southeast Asia, Latin America and Africa may price lower but have fewer qualified firms.

What to do instead: before anyone signs, send the engagement letter to the claims handler and ask for written approval of rates, scope and an initial budget, for example the first 100 hours. Ask in writing how scope extensions get approved.

Mistake four: running the response internally before telling the insurer

Some teams investigate quietly for two or three days, hoping the event is minor, while vendors are brought in and costs build. Most policies require notice "as soon as practicable," and some set fixed deadlines. Costs incurred before notice are the easiest for an insurer to challenge. Prepaid retainers raise a related question: hours burned from a retainer you already paid for may not be reimbursable at all.

What to do instead: notify on suspicion, not confirmation. On most wordings, a notification that turns out to be benign costs you nothing. Ask your broker whether your existing retainer can be recognized under the policy and whether retainer hours used in a covered incident get credited.

Mistakes five and six: letting your MSP run the response and the rebuild

Mistake five: treating MSP hours as incident response costs

For many mid-size companies the MSP is the first call and does most of the early work. But policies often cover response costs only from approved third-party specialists. MSP overtime, extra staff and weekend work may instead fall under business interruption extra expense, which commonly carries a waiting period and is calculated differently. Some insurers also want independent forensics precisely because the MSP's remote management tooling may have been the way in. An MSP investigating itself is a conflict the adjuster will notice.

What to do instead: check whether your wording mentions your IT service provider and under which insuring agreement. On the first call, tell the claims handler what the MSP is doing and ask whether those hours count as response costs, extra expense or neither. Keep MSP time logs separate from business-as-usual billing, with daily entries tied to specific incident tasks.

Mistake six: wiping, rebuilding and upgrading before evidence is preserved

Restoring fast feels responsible. But reimaging servers before forensics captures them can destroy evidence that supports both your claim and your regulatory filings. Using the rebuild to upgrade runs into another clause, the betterment exclusion. Most policies pay to restore systems to their pre-incident standard, not to buy the new endpoint platform or cloud migration you were already planning.

What to do instead: agree a preservation plan with the forensics firm before any rebuild starts. If you want to upgrade during recovery, get the insurer to state in writing what it will contribute, typically like-for-like restoration cost, and budget for the rest yourself.

Mistakes seven and eight: PR before notification and ransom talks without the insurer

Mistake seven: issuing statements before the notification analysis is done

Boards often want a public statement on day one, so an agency is hired and a holding statement goes out. Two problems follow. Crisis communications is often subject to its own sublimit and consent requirement, and agency retainers signed without approval tend to be reduced. And public statements that admit fault or describe data exposure can clash with the policy's no-admission-of-liability condition and with the regulatory notifications counsel is still drafting.

Notification deadlines differ widely by country. The EU and UK GDPR set 72 hours for notifying the supervisory authority. India's CERT-In requires reporting of specified incidents within six hours. Singapore's PDPC expects notification within three calendar days once a breach is assessed as notifiable. Brazil's ANPD regime under the LGPD has its own short timelines. Public messaging has to line up with all that apply to you; verify current deadlines with local counsel. What to do instead: route every external statement through breach counsel, and get the PR firm and its budget approved before the first draft is written.

Mistake eight: negotiating or paying a ransom without written consent

Extortion cover almost always requires the insurer's prior written consent to any payment, and often to the negotiator too. Wordings typically also require sanctions screening (OFAC, the UK's OFSI, EU regimes and other local lists), law enforcement notification, and evidence that payment was a reasonable choice compared with restoring from backups. Some jurisdictions add their own rules, such as ransomware payment reporting obligations for larger businesses in Australia. Extortion costs are recoverable only when every step is documented and approved.

What to do instead: don't open contact with the threat actor yourself. Use a negotiator the insurer has approved, record each consent in writing, and take advice from a licensed professional on sanctions and legality in every country where you operate.

These mistakes happen under pressure, often at 2 a.m., when nobody can find the policy. Fix that before the incident. Work through these steps with your broker at or before renewal:

  1. Extract the consent conditions. List every clause on prior written consent, panel providers, emergency costs, crisis communications, extortion and betterment, with the exact hours, sublimits and rate caps.
  2. Name your vendors. Request a named-provider endorsement for any off-panel forensics firm, law firm or PR agency you would actually use, with agreed rates.
  3. Clarify the MSP's role. Get written confirmation of which insuring agreement, if any, covers MSP work during an incident.
  4. Put the claims hotline in the incident response plan. Make notifying the insurer one of the first five actions, triggered by suspicion rather than confirmation.
  5. Define what "written" means. Confirm whether an email from the claims handler counts as consent (it usually does) and who on your side can request it.
  6. Rehearse it. Run a tabletop exercise each year in which the consent call actually happens, with your broker on the line.

The decision rule for incident day: if a vendor, a rate, a scope change or a public statement hasn't been approved in writing by the insurer, treat it as uninsured until it is. Many adjusters reply within hours. That wait costs far less than absorbing a six-figure disputed invoice.

Frequently asked questions

Does an email from the claims adjuster count as prior written consent?

In most wordings, yes. Email from an authorized claims handler is generally treated as written consent. Check whether your policy names a specific notification address or claims portal, and keep every approval in one shared incident folder so finance can match it to invoices later.

Will my insurer refuse to pay at all if I use a non-panel forensics firm?

Usually not entirely. Many policies pay off-panel costs only up to panel rates, or only if consent was obtained, so you absorb the difference instead of losing the whole claim. A minority of wordings exclude off-panel providers outright, which is why a named-provider endorsement is worth asking for at renewal.

What are emergency costs and how long is the consent-free window?

Emergency costs provisions let you incur response costs without prior consent for a short period after discovery, often 48 to 72 hours. Many limit this to panel providers and cap the amount. After the window closes, normal consent rules apply to everything.

Are my MSP's incident hours covered as incident response costs?

It depends on the wording. Some policies treat MSP work as covered response costs, some treat it as business interruption extra expense subject to a waiting period, and some don't cover it unless the insurer approves it. Ask your broker to confirm in writing which applies before an incident happens.

Can we pay a ransom and claim it back later?

Only if the insurer gave prior written consent and the policy's conditions were met, which usually include sanctions screening, law enforcement notification and documented reasonableness. Paying first and seeking approval afterward is a common reason extortion claims are denied. Get advice from a licensed professional on sanctions and local legality before any payment.

Do consent rules differ between countries?

The consent condition itself is fairly uniform across markets. What changes is everything around it: regulatory notification deadlines, legal privilege for forensic reports, sanctions regimes and ransom-payment reporting rules. Multinationals should confirm with their broker how a global master policy and any local policies interact when an incident touches several countries.

Written by the Breach Risk Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.