Form: Cost-of-Breach DisclosureSource: IBM 2025Filed: 28 Apr 2026
DataBreachCost.comOpen calc
Cost File 10.PR / Per-Record CostIBM CODB 2025 methodology

Cost-component profile

Cost per record: $178 for IP, $115 for anonymized data.

The single most-searched metric in data-breach economics. IBM's 2025 per-record figures run by data type: $178 for intellectual property down to $115 for anonymized customer data, with customer PII (the most commonly compromised type, in 53% of breaches) at $160. IBM publishes per-record cost by data type only, not by industry. The per-record figure is most reliable for mid-volume breaches of roughly 10,000 to 100,000 records; IBM's own study covered breaches of 2,960 to 113,620 records and cautions against multiplying its per-record figures across breaches involving millions of records.

Intellectual property

$178

Costliest record type

Employee PII

$168

IBM 2025

Customer PII

$160

Most commonly stolen (53%)

Anonymized data

$115

Lowest tracked type

Section PR.1

The per-record cost by data class (IBM 2025)

IBM tracks per-record cost by the type of data exposed. The 2025 figures, with 2024 for comparison:

Data class20252024Indicative use
Intellectual property$178$173Source code, model weights, trade secrets
Employee PII$168$189Name, address, SSN, employment data
Customer PII$160$179Name, address, email, phone
Other corporate data$154$171Contracts, financials, internal records
Anonymized customer data$115$132Pseudonymised behavioural records

Source: IBM Cost of a Data Breach Report 2025, Figure 6. Customer PII was the most commonly compromised type, present in 53% of breaches; intellectual property was the costliest per record.

Section PR.2

Sector-level per-record estimates (modeled)

IBM does not publish a per-record cost by industry. Where you see sector per-record figures quoted, they are derived, and so are these. The table below scales IBM's $160 customer-PII per-record figure by each sector's cost ratio against the $4.44M global average (both IBM 2025). Treat them as planning estimates, not IBM data.

IndustryModeled per-record estimateAvg total cost (IBM 2025)Primary regulation
Healthcare~$267$7.42MHIPAA
Financial Services~$200$5.56MPCI DSS / GLBA
Industrial~$180$5MNIST / ICS
Energy~$174$4.83MNERC CIP
Technology~$173$4.79MSOX / GDPR
Pharmaceuticals~$166$4.61MFDA / GxP
Services~$164$4.56MVaries
Entertainment~$160$4.43MVaries
Media~$152$4.22MVaries
Hospitality~$145$4.03MPCI DSS
Transportation~$143$3.98MTSA / CISA
Education~$137$3.8MFERPA
Research~$137$3.79MVaries
Communications~$135$3.75MFCC / GDPR
Consumer~$134$3.72MCCPA / GDPR
Retail~$128$3.54MPCI DSS
Public Sector~$103$2.86MFISMA / FedRAMP

Model: $160 customer-PII per-record baseline x (sector average cost / $4.44M global average), both from IBM CODB 2025. The scaling assumes record-driven costs move proportionally with sector cost, which holds best for notification, credit monitoring, and post-breach response and least well for sectors where business interruption dominates (energy, industrial).

Section PR.3

When per-record cost is reliable

The per-record figure is most reliable for mid-volume breaches in the range of approximately 10,000 to 100,000 records, which matches the range IBM actually studied (2,960 to 113,620 compromised records in the 2025 report). Within this range the per-record cost behaves as a stable multiplier and is the right number to use for back-of-envelope breach-cost estimation. Below the lower bound and above the upper bound the relationship breaks down for different reasons, and IBM's own methodology FAQ states it is not consistent with the research to use per-record cost for breaches involving millions of records.

For breaches below approximately 10,000 records, fixed costs dominate. The cost of forensic investigation does not scale linearly with record count: a forensic engagement for a 1,000-record breach still requires a minimum of $50K-$200K. The cost of legal counsel is similarly fixed at the lower end. The cost of regulator notification is a per-event cost rather than a per-record cost. The result is that effective per-record cost for small breaches can run into the thousands of dollars even though the per-record sector figure is much lower.

For breaches above approximately 100,000 records, fixed-cost amortisation reduces the effective per-record cost materially. Mega-breaches at the 100 million record scale typically show effective per-record cost in the $5-$25 range. The Yahoo breach (3 billion records, approximately $470M total cost) implies a per-record cost of approximately $0.16, far below any benchmark. The Change Healthcare 2024 breach (190 million records, $2.45B+ total cost) implies a per-record cost of approximately $13, again far below the $160 customer-PII figure. The amortisation effect is real and material at scale, which is exactly why IBM warns against extrapolating its per-record figures to mega-breaches.

Section PR.4

How the per-record figure moved in 2025

Per-record costs fell across almost every data class in 2025, mirroring the 9% decline in the global average: employee PII dropped from $189 to $168, customer PII from $179 to $160, other corporate data from $171 to $154, and anonymized customer data from $132 to $115. Intellectual property was the exception, rising from $173 to $178 and overtaking employee PII as the costliest record type.

The decline tracks the same driver as the headline average: faster identification and containment (241 days, a nine-year low) pushed detection and escalation costs down nearly 10%. The IP exception reflects the long-tail competitive damage of stolen source code, model weights, and trade secrets, which faster containment does little to claw back. One related 2025 data point: in shadow-AI incidents specifically, customer PII cost $166 per record, above the $160 global figure for that type.

Section PR.5

Using per-record cost for budget planning

For breach-cost budget planning at a typical mid-market organisation, the per-record cost is the right starting point only within the range IBM actually studied (roughly 3,000 to 113,000 records). For an organisation holding 50,000 customer records, baseline record-driven exposure is $160 x 50,000 = $8M before fixed costs and multipliers; a healthcare provider at the same record count lands nearer $267 x 50,000 = $13.4M on the modeled sector estimate above. Beyond roughly 100,000 records, do not multiply: amortisation takes over and a flat per-record multiplication produces absurd totals (190 million Change Healthcare records x $160 would imply $30B against an actual $2.45B).

The figures above are central estimates. Cyber-insurance underwriters typically apply a wide range around the central estimate to account for breach-specific factors: detection time (breaches over 200 days cost $1.14M more), attack-vector severity (attacker-disclosed extortion runs 14% above average, malicious insiders 11%, per IBM 2025), and control posture (extensive AI/security automation is associated with a $1.9M lower breach cost). For a fully-loaded estimate that accounts for these factors, use the homepage calculator rather than applying the per-record figure as a flat multiplier.

For organisations holding fewer than 10,000 records, the per-record figure is misleading. Use the SMB cost-range data on the small-business page instead, which is calibrated for the fixed-cost-dominated regime.

Cross-references

Schedule F / Reference Q&A

Frequently Asked Questions

Primary source:Per-record cost data from IBM Cost of a Data Breach Report 2025, Figure 6 (2025 and 2024 columns). Sector-level per-record estimates are modeled on this page as described in Section PR.2; IBM does not publish per-record cost by industry.