Chapter 28

Cyber Insurance and Incident Response

Cyber insurance can cover millions in breach costs — or deny your claim entirely. The difference usually comes down to decisions made in the first 48 hours of an incident, decisions that are made by the IR team, not the CFO.

Scenario

48 hours into a ransomware event. Your organization has a $10M cyber insurance policy. The IR lead asks: have we notified the insurer yet? Nobody knows — the CFO handles insurance and they're traveling. Legal thinks the policy says 24 hours. It has been 48. Separately, the IR team engaged an external IR firm without checking whether the insurer has a panel of preferred vendors — the insurer may not reimburse the $180k engagement fee. The ransom is $2M. The policy covers ransom payments but requires insurer pre-approval. Nobody got that approval. At this point, the question is not whether the policy will pay out — it's whether the policyholders fully understand what they bought and what actions they just took that may affect the claim.

What Cyber Insurance Actually Covers

Cyber insurance policies vary significantly by insurer and policy, but most commercial cyber policies cover some combination of first-party losses (your own costs) and third-party liability (claims from others against you). Understanding the structure before an incident determines what IR decisions are within policy scope.

  Cyber Insurance Coverage Structure
  ══════════════════════════════════════════════════════════════════════

  FIRST-PARTY COVERAGE (your organization's losses)
  ──────────────────────────────────────────────────
  ✓ Business interruption: lost revenue during system downtime
    Often the largest payout — systems down for 10 days at $500k/day
    = $5M BI claim alone. Usually requires waiting period (12-72 hours
    of downtime before coverage kicks in).

  ✓ Extra expenses: costs to maintain operations during recovery
    Temporary cloud infrastructure, overtime, emergency vendor costs

  ✓ IR costs: external IR firm fees, forensic investigation costs
    CRITICAL: many policies require use of insurer's panel vendors
    Engaging a vendor not on the panel may not be reimbursed

  ✓ Ransomware payment: payment to recover data/restore systems
    CRITICAL: requires pre-approval from insurer; OFAC check required
    Some policies have sublimits ($1M on a $10M policy for ransom)

  ✓ Crisis communications: PR firm fees during breach
  ✓ Notification costs: mailing, call center, credit monitoring
  ✓ Cyber extortion negotiator fees

  THIRD-PARTY COVERAGE (claims against you)
  ──────────────────────────────────────────
  ✓ Liability to others for data breach (class actions, regulatory fines)
  ✓ Regulatory defense costs and fines (GDPR fines often excluded)
  ✓ Media liability: defamation, privacy violations via media

  COMMON EXCLUSIONS
  ──────────────────
  ✗ War exclusion: attacks attributed to nation-states
    (Merck/NotPetya: $1.4B claim denied, later settled)
  ✗ Negligence: failure to maintain basic security controls
    (MFA disabled, unpatched critical vulnerabilities)
  ✗ Social engineering sublimits: BEC often has much lower coverage
  ✗ Pre-existing conditions: breaches that started before policy period
  ✗ GDPR fines: explicitly excluded in many policies
  ✗ Intellectual property theft: often not covered

The Notification Window

Most cyber insurance policies require notification within a specified window — typically 24 to 72 hours after the policyholder becomes aware of a potential covered incident. Missing this window is the single most common reason for coverage disputes. Every IR team member needs to know this number for their organization's policy before an incident occurs.

Mistake: confusing "when we know it's serious" with "when we know there's an incident"

The notification clock typically starts when the organization becomes aware of a "potential" covered incident — not when they have confirmed it is a significant breach. If your EDR fires a ransomware alert, even if you're not sure if it's a real incident, the conservative interpretation of most policies is that the notification clock started at the moment of that alert. Organizations that wait until they've confirmed the severity before notifying — 24 or 48 hours later — may find themselves outside the notification window. The correct approach: notify the insurer at the same time you're escalating internally. Many insurers have 24/7 hotlines specifically for this. Notification does not commit you to making a claim; it preserves the option. Not notifying within the window may waive coverage.

  First 24 Hours: IR + Insurance Actions in Parallel
  ══════════════════════════════════════════════════════════════════════

  T+0:   Incident confirmed or credibly suspected
         ↓
  T+1h:  Simultaneously:
         ├── IR: out-of-band comms, initial containment
         ├── Legal: litigation hold, attorney privilege established
         └── Insurance: notify insurer via policy hotline
                        (get confirmation number, document the call)
         ↓
  T+4h:  Initial insurer conversation:
         ├── Confirm coverage type and limits
         ├── Get list of panel IR firms (if you haven't engaged one yet)
         ├── Ask about ransomware pre-approval process
         └── Establish claims contact / point of contact
         ↓
  T+12h: If not already engaged: choose IR firm from panel
         (or get approval for non-panel firm before engaging)
         ↓
  T+24h: If ransomware: pre-approval for payment if applicable
         (may require ransom amount, OFAC check, insurer review)

  Key principle: the insurer is a stakeholder from T+1h, not T+72h.
  Loop them in early and keep them updated throughout.

Panel IR Firms and Vendor Pre-Approval

Most cyber insurers maintain a panel of preferred vendors — IR firms, forensic labs, law firms, and crisis communications firms — that they have vetted and have pre-negotiated rates with. Using panel vendors simplifies claims processing and ensures reimbursement. Using non-panel vendors creates a reimbursement risk that can result in a significant bill the insurer won't cover.

Vendor typePanel importanceHow to manage
External IR firmHigh — largest single cost item; non-panel firms may not be reimbursedKnow your insurer's panel before an incident. If you have a retainer with a non-panel firm, get pre-approval added to your policy at renewal.
Forensic labMedium — typically used by the IR firm; if you control this choice, use a panel labAsk panel IR firms which labs they work with.
Outside counsel (privacy/breach)High — breach response counsel fees are significant; panel firms have pre-negotiated ratesSame as IR firm: know the panel, pre-approve your preferred firm if off-panel.
Crisis communications firmMedium — some policies have sublimits for crisis comms; check coverage firstConfirm coverage scope before engaging a PR firm.
Credit monitoring vendorLow — most insurers accept standard providers without pre-approvalConfirm acceptable vendors with insurer during early notification call.

Ransom Payment Pre-Approval

If your organization decides to pay a ransom, and the policy covers ransom payments, that payment almost certainly requires pre-approval from the insurer. The insurer will conduct an OFAC sanctions check (they have legal exposure too if they fund payment to a sanctioned entity), review the demand, and in some cases negotiate on your behalf or through their preferred negotiator. This process takes time and must be started before payment, not after.

  Ransom Payment Pre-Approval Process
  ══════════════════════════════════════════════════════════════════════

  1. Decision made to consider ransom payment
     (by CISO + CEO + Legal — not IR team alone)
     ↓
  2. Notify insurer immediately
     Provide: ransom demand amount, cryptocurrency requested,
     payment deadline given by attacker (if any),
     ransomware group identification
     ↓
  3. Insurer performs OFAC check
     Time: 2-4 hours typically
     Result: cleared (can proceed) or flagged (do not pay)
     ↓
  4. Negotiation (if applicable)
     Insurer may deploy their preferred negotiator
     Some insurers negotiate on all ransomware claims
     Goal: reduce ransom demand (typically 20-60% reduction possible)
     Time: 24-96 hours depending on attacker responsiveness
     ↓
  5. Insurer pre-approves payment amount
     Get written pre-approval before executing payment
     Verbal pre-approval is not sufficient for claims purposes
     ↓
  6. Payment executed
     Document: cryptocurrency transaction ID, wallet addresses,
     exact amount paid, timestamp
     ↓
  7. Claim submission with payment documentation
     Insurer reimburses per policy terms (may have waiting period
     before reimbursement, deductible applies)

  WARNING: paying before OFAC clearance or insurer pre-approval
  risks claim denial AND potential federal liability for OFAC violation
Why insurers have become stricter about ransomware coverage

Between 2019 and 2022, ransomware claims drove combined ratios above 100% for many cyber insurers — they paid out more than they collected in premiums. The industry responded with significant changes: higher premiums, lower limits, sublimits on ransomware specifically (some policies now have $1M ransomware sublimits on $10M policies), stricter security control requirements for coverage (MFA is typically now a hard requirement for renewal), and more stringent pre-approval processes. Organizations that renewed policies in 2020 with generous ransomware coverage may find their 2024 renewal looks very different. The practical implication for IR teams: know your current policy's ransomware terms, not last year's terms. The coverage landscape has shifted significantly.

The Claims Process

After the incident is contained and remediated, the claims process begins. How well the IR team documented everything during the incident directly determines how smoothly the claim goes and how much is ultimately reimbursed.

Claim componentDocumentation requiredCommon dispute points
Business interruptionRevenue records pre-incident vs during downtime; documented downtime log per system; documentation that systems were down due to incident (not scheduled maintenance)Quantifying lost revenue; waiting period disputes; whether downtime was "caused by" the incident or pre-existing issues
IR firm feesEngagement letter, invoices, time and materials records, written authorization from insurer if non-panel firmNon-panel firms; scope creep beyond what was pre-approved; fees for work done before notification
Ransomware paymentPre-approval in writing, cryptocurrency transaction records, wallet addresses, exchange records, all negotiation communicationsPayment made before pre-approval; OFAC issues; payment exceeding approved amount
Notification costsVendor invoices, notification letter drafts, mailing records, credit monitoring enrollment numbersNotification sent before confirming coverage; notification of customers who may not trigger obligation
Forensic costsLab invoices, scope of work documentationNon-panel labs; forensic work done for litigation preparation (may not be covered separately)

Insurance and Security Controls: The Coverage Condition

Post-2022, cyber insurers have become significantly more rigorous about security control requirements as conditions of coverage. The most common: multi-factor authentication, endpoint detection, email filtering, network segmentation, and backup testing. Misrepresenting your security controls on the application — or implementing them after the application but before renewal — creates a coverage risk that can result in rescission of the entire policy.

Mental model: the insurance application as a security audit

When your organization fills out a cyber insurance application, every answer is a warranty about your security posture. If the policy is later invoked and the insurer's coverage team investigates, they will compare the state of your environment at the time of the breach against the representations made in the application. If MFA was represented as "deployed for all remote access" but the breach involved an account without MFA on a VPN server, that misrepresentation is grounds for coverage denial. This means the IR team has a role in policy procurement: the people who actually know whether MFA is truly deployed everywhere, whether backups are actually tested, and whether EDR is actually on all endpoints should be the ones answering those questions on the application — not a procurement team member who doesn't have that knowledge.

Q & A

Q: The insurer's panel includes only three IR firms, none of which you have a relationship with. You've been working with a non-panel firm for years and trust them. How do you handle this?

Address it before the incident, not during: (1) At renewal, ask your broker to negotiate an endorsement to the policy that names your preferred firm as a covered vendor. Many insurers will do this — they want to preserve the relationship with you as a customer. The endorsed firm typically agrees to the insurer's rate structure. (2) If an incident occurs before you've done this: call the insurer immediately, explain the existing relationship, and ask for emergency approval to use your preferred firm. Insurers sometimes grant this, especially if the non-panel firm is reputable. Get the approval in writing before any fees are incurred. (3) If the insurer won't approve the non-panel firm: you have a choice — use a panel firm (insurer pays), use your preferred firm (you may pay the difference), or use a hybrid (panel firm as lead with your preferred firm in an advisory role). The hybrid approach can work but requires clear scope separation and written insurer approval. (4) For future planning: evaluate whether your preferred IR firm has a relationship with any of your potential insurers. Many major IR firms (Mandiant, CrowdStrike, Unit 42) are on multiple insurer panels.

Q: The insurer's coverage decision takes 10 days. You need to start remediation now. Can you proceed with remediation before the coverage determination?

Yes, with documentation and pre-authorization where possible: (1) The insurer generally cannot require you to delay remediation that is necessary to stop ongoing damage or meet security and regulatory obligations. You are not required to remain compromised while the coverage determination is made. (2) Document everything before you remediate. Forensic images, evidence inventory, chain of custody — complete this before any wipe/reimage cycle. If evidence is destroyed in the course of remediation before the insurer's investigators have had a chance to review it, that can complicate the claim. (3) Inform the insurer that remediation is proceeding. Get written acknowledgment that they are aware you are remediating. This prevents a later claim dispute argument that you destroyed evidence. (4) Keep detailed records of all remediation costs — labor hours, replacement hardware, software licenses, cloud infrastructure costs. These will be part of the claim. (5) If there is a specific forensic investigation the insurer wants to conduct, ask whether it can be done in parallel with remediation rather than as a prerequisite to it. Most skilled forensic investigators can work from forensic images rather than live systems.

Q: Your insurer is pushing hard for you to pay the ransom quickly, saying it's the fastest resolution. You're not sure it's the right call. What do you do?

The insurer has a financial stake in the outcome but that doesn't make them the decision-maker: (1) The insurer's incentive structure: a quick ransom payment at $500k may be cheaper for the insurer than a 3-week IR engagement at $300k/week plus business interruption at $200k/day. Their recommendation to pay quickly may reflect their cost model, not necessarily your best interests or the best security outcome. (2) Your interests may differ: paying quickly may discourage thorough forensics — if you pay and restore quickly, you may not fully understand the initial access vector or whether the attacker left other backdoors. You also don't know whether payment will actually restore your data. (3) Decision authority: the ransom payment decision belongs to your executive team (CISO, CEO, general counsel) — not to the insurer. The insurer's role is to provide coverage; the decision-making authority stays with you. (4) Get a second opinion: engage your own legal counsel and IR firm to provide their independent assessment of the payment decision versus backup restoration. Make the decision based on your full information set, not just the insurer's recommendation. (5) Document the insurer's recommendation and your rationale for whatever decision you make. If you decide not to follow their recommendation, document why. This protects you in any later coverage dispute.

Q: Post-incident, the insurer's forensic investigator wants access to your systems and all IR documentation to evaluate the claim. How much access are you required to give?

Your policy will specify this — read it carefully and have legal review before granting access: (1) Cooperation clauses: nearly all cyber policies have a cooperation clause requiring the policyholder to cooperate with the insurer's investigation and provide access to records, systems, and personnel. Failing to cooperate can be grounds for claim denial. However, "cooperate" has limits — it doesn't mean unlimited access to everything. (2) Scope the access: what specifically does the insurer need? Evidence related to the breach and the claimed costs — yes, required. Access to systems unrelated to the breach, or documents covered by attorney-client privilege — no. Work with legal to define the scope of cooperation that satisfies the cooperation clause without providing unnecessary access. (3) Attorney-client privilege: communications between you and your legal counsel about the incident are privileged and cannot be required by the insurer. The insurer's forensic investigator is not your attorney; conversations with them are not privileged. Everything you say to the insurer's team is potentially discoverable by plaintiff attorneys in civil litigation. (4) The adversarial possibility: in large claims, the insurer's investigation is partly aimed at finding grounds to deny or reduce the claim — not just at verifying your losses. Their forensic investigator is working for the insurer, not for you. Treat the investigation accordingly and involve your legal team in the access decisions.