Cyber Breach Cost Calculator
Estimate direct breach-response, record, downtime and uninsured costs.
Last updated: November 5, 2026
Starting figures illustrate this model. Enter your own measurements, quoted costs and applicable terms; this page does not retrieve live prices or provider rates.
Estimated net breach cost
—
- Gross breach cost: —
- Downtime loss: —
- Insurance reimbursement: —
On this page
Quick summary: Estimate direct breach-response, record, downtime and uninsured costs.
Read the complete guide
Updated reference sections in this guide are in English.
What this calculator estimates
Estimate direct breach-response, record, downtime and uninsured costs.
How to use it
Enter Affected records; Estimated cost per affected record ($); Downtime hours; Revenue or contribution margin lost per hour ($); Forensics, legal, notification and PR cost ($); Expected cyber-insurance reimbursement ($). Select Calculate to update the results.
How the calculation works
Affected-record cost, downtime loss and response expenses are totaled, then expected insurance recovery is subtracted.
Worked example: starting scenario
| Affected records | 25000 |
|---|---|
| Estimated cost per affected record ($) | 180 |
| Downtime hours | 36 |
| Revenue or contribution margin lost per hour ($) | 12000 |
| Forensics, legal, notification and PR cost ($) | 650000 |
| Expected cyber-insurance reimbursement ($) | 1500000 |
| Estimated net breach cost | $4,082,000.00 |
|---|---|
| Gross breach cost | $5,582,000.00 |
| Downtime loss | $432,000.00 |
| Insurance reimbursement | $1,500,000.00 |
Important limitations
Fines, litigation, business interruption, policy exclusions and reputational loss may differ substantially.
A scenario budget, not a breach forecast
Separate incident-response and legal bills from business interruption. Lost revenue is not automatically lost profit: use the revenue or cost basis named by each input and avoid counting the same outage in two fields. Notification, customer support and recovery scope can change independently, so a single entered scenario does not measure the probability of a breach.