The 90-Minute Breach: Nine Money Questions to Answer After a Cybersecurity Incident

Archi4 min read

cybersecuritybudgetbreachinsurance

Contents
  1. The First 90 Minutes Are Cheap. The Next 90 Days Are Not.
  2. 1. Incident Response Retainer: What Did You Already Pay For?
  3. 2. Legal Counsel: The Meter Runs From the First Phone Call
  4. 3. Customer Notification: Postage, Print, and Call Centers
  5. 4. Downtime: The Revenue You Did Not Book
  6. 5. Overtime and Contractor Backfill
  7. 6. Regulatory Fines and Penalties: The Long Tail
  8. 7. Cyber Insurance: Read the Sub-Limits Before You Need Them
  9. 8. Customer Churn and Discounts
  10. 9. The Fix: What You Will Spend to Prevent the Next One
  11. A Simple Tally Sheet
  12. What to Do This Week

The First 90 Minutes Are Cheap. The Next 90 Days Are Not.#

Most cybersecurity incidents follow a pattern: a quick detection, a frantic containment, then a long, expensive aftermath that few teams budget for. The average cost of a data breach has hovered around $4.5 million for years, according to IBM's annual survey, but that number hides the line items that matter. This checklist is built around the money, not the malware. Use it after the initial fire is out, and use it to argue for budget before the next one.

1. Incident Response Retainer: What Did You Already Pay For?#

If you have a retainer, the clock started when you called. If you do not, you are buying hours at emergency rates, often triple the normal consulting fee. Ask your provider for a line-item breakdown: hours worked, roles billed, and any travel or tooling surcharges. A single forensics firm can bill $400 to $600 per hour per consultant. Two consultants for a week is already a five-figure line item.

Outside counsel is often required to direct the investigation and preserve privilege. That means partner-level billing from day one. Ask for a budget estimate and a cap. Legal fees for a mid-sized breach can easily exceed the forensics bill, especially if regulators or multiple state attorneys general get involved.

3. Customer Notification: Postage, Print, and Call Centers#

If you have to notify 10,000 people, the math is not just stamps. Print and mail runs $1 to $2 per letter. A call center for worried customers costs $5 to $10 per contact. Credit monitoring for a year is often $10 to $20 per person. Multiply by your affected population and add 20 percent for the people who call twice. For a 10,000-person breach, this bucket alone can hit $150,000 before you count staff time.

4. Downtime: The Revenue You Did Not Book#

This is the number executives feel fastest. Estimate the hours systems were unavailable, multiply by average hourly revenue, and add overtime for staff who worked through the weekend. Do not forget the deals that slipped. A sales team locked out of CRM for two days often loses more in pipeline than in direct downtime. Track it as a separate line so you can compare it to the cost of prevention.

5. Overtime and Contractor Backfill#

Your security team will work double shifts. Your IT staff will cover the gap. Add overtime pay, contractor day rates, and the cost of backfilling normal work that got dropped. A common mistake is to treat this as free because it comes out of existing salaries. It is not free. It is deferred work that will surface later as missed deadlines or burnout-driven turnover.

6. Regulatory Fines and Penalties: The Long Tail#

Fines rarely arrive in the first quarter. Under GDPR, penalties can reach 4 percent of global annual revenue. In the United States, state breach laws and sector regulators (healthcare, finance) each have their own schedules. Budget for a multi-year legal reserve even if the initial number looks small. The fine is often less than the cost of the lawyers who negotiate it.

7. Cyber Insurance: Read the Sub-Limits Before You Need Them#

Most policies have sub-limits for ransomware, social engineering, and notification costs. A $5 million policy might cap notification expenses at $500,000. Check whether your forensics vendor is on the insurer's panel. If not, you may pay out of pocket and fight for reimbursement later. The claims process itself takes months and generates its own paperwork costs.

8. Customer Churn and Discounts#

This is the hardest number to pin down and the one most often ignored. After a breach, some customers leave, some demand discounts, and some require extra security questionnaires before renewal. Pull your churn data for the 90 days after the incident and compare it to the same period last year. Add the cost of any retention discounts you offered. A 2 percent churn bump on a $20 million book of business is $400,000 in lost recurring revenue.

9. The Fix: What You Will Spend to Prevent the Next One#

Finally, add the cost of the remediation you promised. New endpoint tools, identity upgrades, extra headcount, and a tabletop exercise all have price tags. This is the line item that often gets cut when the emergency fades. Do not let it. The cheapest time to fund prevention is while the invoice for the incident is still on the CFO's desk.

A Simple Tally Sheet#

Build a spreadsheet with these nine rows and a column for estimated and actual. Update it weekly during the response and monthly after. Share it with finance, not just security. The goal is not to assign blame. It is to make the trade-offs visible. A breach that costs $800,000 in forensics and downtime but triggers $50,000 in prevention spending is a story about priorities, not technology.

What to Do This Week#

Pull your incident response contract and check the hourly rates. Ask your insurance broker for the sub-limits in writing. Run a tabletop exercise with a finance lead in the room and a stopwatch on the table. The numbers you write down in a calm meeting are far more useful than the ones you guess at during a crisis.

More articles