Skip to content
FinToolSuite
Updated May 14, 2026 · Cloud & Tech · Educational use only ·

Data Breach Cost Calculator

What a breach really costs.

Calculate total data breach cost across notification, forensics, regulatory fines, and customer churn at a per-record cost assumption.

What this tool does

This calculator models the total financial impact of a data breach by combining multiple cost categories into a single figure. It takes the number of records exposed and multiplies by a per-record cost, then adds regulatory fines, technical remediation expenses, and estimated revenue loss from reputational damage. The result shows the combined all-in cost across these areas. The per-record cost and reputational revenue loss typically have the largest influence on the final total. The calculation is useful for understanding breach scenarios in different organisational contexts—for example, comparing cost impacts across breach sizes or remediation approaches. Note that this model treats each cost component as independent; actual breach costs may vary based on factors like time to detection, industry-specific regulations, customer retention rates, and market conditions, which lie outside this calculation's scope. The output is for educational illustration and cost modelling only.


Enter Values

People also use

Formula Used
Records
Per record
Fines
Remediation
Rep loss

Spotted something off?

Calculations or display — let us know.

Disclaimer

Results are estimates for educational purposes only. They do not constitute financial advice. Consult a qualified professional before making financial decisions.

Data breach costs extend beyond direct records. IBM 2024 report: 150 average per record + regulatory fines + remediation + lost business. This calculator sums all components.

10,000 records × 150 + 50,000 fines + 80,000 remediation + 200,000 lost revenue = 1,830,000 total breach cost. For most SMBs this is existential without insurance.

Use to justify security investment. Breach cost vs annual security spend makes prioritisation clearer. Even 1% breach probability reduction saves many multiples of typical security spend.

Quick example

With records exposed of 10,000 and cost per record of 150 (plus regulatory fines of 50,000 and remediation cost of 80,000), the result is 1,830,000.00. Change any figure and watch the output shift — it's often more useful to see the pattern than to memorise the formula.

Which inputs matter most

You enter Records Exposed, Cost per Record, Regulatory Fines, Remediation Cost, and Reputational Revenue Loss.

What's happening under the hood

Total = records × per-record + fines + remediation + reputational loss. The formula is listed in full below. If the number looks off, you can retrace the calculation by hand — that's the point of showing the working.

What to do with a low result

A disappointing result is information, not a judgement. Pick the single input that dragged the figure down most and focus the next quarter on that one factor. Breadth-first improvement rarely works; depth-first on the worst input usually does.

What this doesn't capture

The score is a composite of the inputs you provide. Life context — job security, family obligations, health, housing — doesn't appear in the math but shapes the real picture. Use the number as a prompt, not a verdict.

Worked example

Suppose a mid-sized organisation experiences a breach affecting 5,000 customer records. Here's how the components stack:

  • Records exposed: 5,000
  • Cost per record: 150 (covering forensic investigation, notification, and credit monitoring)
  • Regulatory fines: 75,000 (penalty for non-compliance with data protection rules)
  • Remediation cost: 120,000 (security assessment, system upgrades, staff training)
  • Reputational revenue loss: 300,000 (estimated customer churn and lost sales over 12 months)

Total calculated cost: 5,000 × 150 + 75,000 + 120,000 + 300,000 = 1,200,000. This single incident represents a material financial event for many organisations.

Common scenarios where this matters

The calculator proves useful in several contexts:

  • Budget justification: Compare annual security investment against a single-breach scenario. The gap often clarifies ROI on preventative spending.
  • Risk comparison: Model different breach sizes (1,000 vs 10,000 vs 50,000 records) to understand exposure tiers.
  • Insurance evaluation: Test whether coverage limits align with realistic breach costs across your data holdings.
  • Board reporting: Illustrate breach impact in financial terms rather than abstract risk language.

What this result captures and what it doesn't

The calculator aggregates five major cost dimensions: per-record expenses, fines, technical remediation, and revenue impact. It models these as separate line items that sum to a total.

What it does not include: legal fees beyond remediation, employee time diverted during incident response, long-term customer lifetime value erosion, competitive disadvantage from lost trust, operational downtime costs, or third-party notification service fees. Different breaches trigger different subsets of these costs; the model offers a framework rather than a complete forecast.

Educational illustration

This calculator models potential breach costs for educational purposes. The output shows how different inputs combine mathematically. Actual breach costs vary based on industry, jurisdiction, data sensitivity, response speed, and contractual obligations. Use this figure to inform risk assessment, not as a binding estimate.

Example Scenario

10,000 × ££150 + ££50,000 + ££80,000 + ££200,000 = 1,830,000.00.

Inputs

Records Exposed:10,000
Cost per Record:£150
Regulatory Fines:£50,000
Remediation Cost:£80,000
Reputational Revenue Loss:£200,000
Expected Result1,830,000.00

This example uses typical values for illustration. Adjust the inputs above to match a specific situation and see how the result changes.

Sources & Methodology

Methodology

The calculator computes total breach cost by summing four primary components. It multiplies the number of records exposed by the cost per record, then adds regulatory fines, remediation expenses, and estimated reputational revenue loss. The model treats each cost category as independent and additive, applying no discounting or time-weighting across phases. It assumes the cost per record applies uniformly regardless of data type or breach scale, and that all costs materialize within a single period. The calculator does not account for indirect costs such as legal fees beyond remediation, ongoing monitoring expenses, potential insurance recovery, tax deductibility, or variations in regulatory fines based on jurisdiction or breach severity. Results represent an aggregate estimate rather than a prediction of actual organizational impact.

Frequently Asked Questions

What drives GDPR fines?
Up to 4% of annual global revenue OR 20M, whichever higher. Actual fines depend on severity, cooperation, prior violations. Most SMB fines are 50k-500k range; tech giants have paid hundreds of millions.
What is a typical cost per record and how does it affect the total?
Industry research such as IBM's annual Cost of a Data Breach Report places the global average per-record cost in the range of 150-200 USD, though figures vary significantly by industry, data sensitivity, and geography. Because this figure is multiplied by the full record count, even small changes to the per-record input produce large swings in the total output, making it the single most influential variable in the model.
Why does the calculator treat all cost components as independent and additive?
The additive structure keeps the model transparent and straightforward to audit, allowing each cost category to be adjusted without affecting the others. In reality, breach costs can interact—larger breaches may attract higher fines and greater reputational damage simultaneously—so the independent assumption is a simplification that trades accuracy for interpretability. Users comparing scenarios should consider the output to be a relative indicator rather than a precise organisational forecast.
Can this calculator be used to estimate costs for breaches of different sizes or industries?
The calculator supports scenario comparison by adjusting inputs such as record count, per-record cost, and remediation expenses to reflect different breach scales or sector contexts—for example, healthcare organisations typically carry higher per-record costs due to regulatory and notification obligations. However, the model applies a uniform per-record cost regardless of data type or volume, and does not incorporate industry-specific regulatory multipliers or breach-scale discounts, so results across very different contexts should be interpreted with that limitation in mind.

Related Calculators

More Cloud & Tech Calculators

Explore Other Financial Tools