PII Exposure Calculator
Quantify PII breach exposure: records at risk, field sensitivity, identity-theft potential, notification cost and regulatory fines.
Inputs
Total Exposure Cost
$16,446,000
Field Sensitivity Index
5.40/ 10
Identity Theft Potential
64.0%
Notification and Support
$3,000,000
Remediation and Monitoring
$12,150,000
Maximum Regulatory Fine at 4% of Revenue
$16,000,000
Cost per Record
$65.78
Step by step
Values used
Records exposed = 250,000 records; Names and email addresses included = Yes; Government identifiers included = Yes; Payment or bank details included = No; Health data included = No; Passwords or authentication secrets included = Yes; Protection applied to the exposed data = Unsalted or fast hashes — 0.7; Notification and support cost per record = 12 currency/record; Credit monitoring and remediation per record = 45 currency/record; Annual revenue = 400,000,000 currency
PII Exposure
sensitivityIndex = 0.9 × (1 for names/email + 3 for government ID + 3 for financial + 2.5 for health + 2 for credentials); costs scale notification and remediation by record count and sensitivity.
Modelled regulatory exposure
expectedFine = maxFine × min(0.15, sensitivityIndex ÷ 10 × 0.15) — enforcement rarely reaches the statutory maximum, so the model caps the modelled exposure at 15% of it.
Total Exposure Cost
= 16,446,000
Field Sensitivity Index
= 5.40 / 10
Identity Theft Potential
= 64.0
Notification and Support
= 3,000,000
Remediation and Monitoring
= 12,150,000
Maximum Regulatory Fine at 4% of Revenue
= 16,000,000
How it works
What makes a breach expensive is the field combination, not the record count alone: a name and email is a nuisance, while a name with a government identifier is a durable identity-theft kit that cannot be reissued like a card number. Credential exposure is discounted by how well the secrets were protected, which is the one field where prior engineering decisions materially change the outcome. Fine exposure is modelled well below the statutory maximum because enforcement rarely reaches it. Cost per record is the figure that survives contact with a board: it converts an abstract breach into a number that can be compared against the cost of the control that would have prevented it.
Formulas
PII Exposure
sensitivityIndex = 0.9 × (1 for names/email + 3 for government ID + 3 for financial + 2.5 for health + 2 for credentials); costs scale notification and remediation by record count and sensitivity.
- sensitivityIndex
- Weighted sensitivity of the exposed field combination
- identityTheftRisk
- Probability the combination supports identity theft, reduced where credentials were properly hashed
- maxFine
- 4% of annual revenue, the GDPR upper tier
Modelled regulatory exposure
expectedFine = maxFine × min(0.15, sensitivityIndex ÷ 10 × 0.15) — enforcement rarely reaches the statutory maximum, so the model caps the modelled exposure at 15% of it.
- maxFine
- Statutory ceiling
- sensitivityIndex
- Drives how seriously the exposure is treated
Frequently Asked Questions
How is PII Exposure calculated?
sensitivityIndex = 0.9 × (1 for names/email + 3 for government ID + 3 for financial + 2.5 for health + 2 for credentials); costs scale notification and remediation by record count and sensitivity. What makes a breach expensive is the field combination, not the record count alone: a name and email is a nuisance, while a name with a government identifier is a durable identity-theft kit that cannot be reissued like a card number. Credential exposure is discounted by how well the secrets were protected, which is the one field where prior engineering decisions materially change the outcome. Fine exposure is modelled well below the statutory maximum because enforcement rarely reaches it.
Why does PII Exposure matter?
Cost per record is the figure that survives contact with a board: it converts an abstract breach into a number that can be compared against the cost of the control that would have prevented it.
What values do I need to enter?
This calculator takes 10 inputs: Records exposed, Names and email addresses included, Government identifiers included, Payment or bank details included, Health data included, Passwords or authentication secrets included, Protection applied to the exposed data, Notification and support cost per record, Credit monitoring and remediation per record, Annual revenue. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Why is a government identifier weighted above payment data?
Because it cannot be reissued. A compromised card is cancelled in a day; a national identifier follows the person for life and underpins account opening everywhere, which is why remediation costs run for years.
Are these per-record figures reliable?
They are planning figures, not actuals. Published averages hide enormous variation by sector and jurisdiction, so replace the defaults with your own legal and notification quotes as soon as you have them.
You might also need
- Ransomware Impact CalculatorCommonly used together
- Privacy Risk CalculatorCommonly used together
- LLM Data Leakage Risk CalculatorCommonly used together
- Data Loss Prevention Coverage CalculatorCommonly used together
- Insider Threat Risk CalculatorCommonly used together
- Quantum Threat Readiness CalculatorAlso in Forensics & Emerging Threats