• SOC 2 Readiness
  • 24/7 incident line
  • 24/7 security operations team

Risk assessment tool

Data Breach Cost Calculator

Estimate the financial impact of a security breach on your organization, using figures from IBM's Cost of a Data Breach Report 2026.
An incident response team working around a table with a timeline on a whiteboard

Breach Parameters

50,000
1,000100K1M10M

Still needed: industry, country, security maturity, incident response plan.

Your breach cost estimate will appear here

Fill out all fields and click Calculate Breach Cost to see the potential financial impact on your organization.

How to Reduce Your Risk

Every security investment reduces breach likelihood or total cost. Here is how GuardsArm services directly impact your exposure.

MDR / SOC

Round-the-clock monitoring and response shortens the time between an intrusion and containment, which is where much of the detection and escalation cost comes from.

Learn more

Penetration Testing

Find and fix exploitable weaknesses before an attacker uses them to reach your records.

Learn more

Employee Training

Phishing and social engineering remain common ways in. Training and simulations help staff recognize and report them.

Learn more

Incident Response Planning

A tested plan means decisions about containment, notification and recovery are made in advance, not in the middle of an incident.

Learn more

What each input means

The estimate is only as good as the answers. Here is what each field is asking for and how to answer it.

Industry

Scales the cost per record by how your sector's average breach compares with the global average in IBM's 2026 study (healthcare, financial services, technology and industrial are broken out; other sectors use the global average).

Number of records

How many records containing personal or confidential data could be exposed in one incident. Count customers, patients, employees, applicants and former customers kept in archives and backups. Use unique individuals, not database rows.

Country

IBM reports average breach costs of USD 5.20M in Canada and USD 11.5M in the United States, against a global USD 4.99M. Choose where most of the affected people live, since that is where notification and regulatory obligations fall.

Security maturity

Together with the response plan, this sets the readiness adjustment. IBM found breaches contained within 200 days averaged USD 4.32M and longer ones USD 5.65M. If you are unsure, take the cybersecurity maturity assessment first.

Incident response plan

Whether you have a written plan and whether it has been rehearsed. A plan that has never been exercised counts as untested, however detailed it is.

How to read your estimate

  1. Start with a realistic scenario

    Model the breach you would actually worry about, such as a compromised file share or a stolen customer database, not every record you have ever held.
  2. Compare it with the baseline

    The comparison badge shows how your estimate sits against the same number of records at IBM's global cost per record, with no sector, country or readiness adjustment.
  3. Change one input at a time

    Move the response plan from none to tested, or maturity up one step, and watch the total. The difference is a rough indicator of what preparation is worth to you.
  4. Use the breakdown to assign owners

    Detection, escalation and lost business point to security operations and leadership; notification and post-breach response point to privacy, counsel and communications.

What the estimate leaves out

Some of the largest breach costs do not scale with the number of records. Add these to your planning separately.
  • Ransom or extortion payments and the cost of negotiating them
  • Extended operational downtime that is not tied to record counts
  • Contractual penalties owed to customers or partners
  • Payment card forensic investigations and card brand assessments
  • Class action defence and settlements
  • Your cyber insurance retention or deductible, and any change in premium

Next steps after you have a number

The quickest way to lower the figure is to lower the record count. Delete data you no longer need, separate the systems that hold the most sensitive records, and restrict who can export them. Every record you do not hold is one you never have to notify about.

Next, look at the two multipliers you control directly. Write or update your incident response plan and run a tabletop exercise so it counts as tested, then work on detection, which the breakdown shows as one of the largest shares. Our incident response planning team can help with both, and the maturity assessment gives you a better basis for the maturity input.

Finally, check your cover. The cyber insurance readiness checklist lists the controls underwriters commonly ask about, and the incident response preparedness checklist shows whether your team could act on the plan at short notice.

Data Breach Cost Calculator: Frequently Asked Questions

How does the calculator produce its estimate?

It multiplies the number of records by IBM's 2026 cost per customer record (USD 192), then scales it by how your sector and country compare with IBM's global average breach cost, and by a readiness adjustment based on IBM's finding that faster-contained breaches cost less. The total is split using IBM's finding that detection, escalation and lost business make up 63% of breach cost. IBM's per-record figures fit breaches of up to about 115,000 records; above that the estimate is likely to overstate the cost.

How accurate is the result?

Treat it as an order of magnitude for planning, not a forecast. Real breach costs depend on how long the attacker was present, what data was taken, contracts, legal action and how the incident is handled. The calculator is most useful for comparing scenarios and showing how preparation changes the picture.

What counts as a record?

Any record about an identifiable person or a confidential business matter that would need to be investigated, and possibly reported, if exposed. A customer with an account, an order history and a support ticket is one person, so count them once.

What notification obligations could apply?

In Canada, PIPEDA requires organizations to report breaches of security safeguards that create a real risk of significant harm to the Privacy Commissioner of Canada, notify affected individuals and keep a record of every breach. Alberta PIPA has a similar duty to notify the provincial Commissioner. In the US, the HIPAA Breach Notification Rule and state breach laws set their own tests and deadlines. Get legal advice on which apply to you.

Can I use the number with my insurer or board?

It can start the conversation, for example when discussing whether your cyber policy limits are in the right range. For a decision that matters, back it with your own data: record counts by system, contract terms and a review of your incident response capability.

Is any of my information stored?

No. The calculation runs in your browser and nothing you enter is sent to us.

Ready to reduce your breach risk?

GuardsArm helps organizations build security programs that prevent breaches and limit the damage when incidents occur.