CASE FILE // PC-2026-04
Status: Open


Filing 03.01.00Field 27 APR 2026Classification PublicStatus Open

Phishing cost in healthcare: $9.77M average, 14 years at the top of the table

Healthcare has held the highest sector breach cost in every IBM Cost of a Data Breach report since the report began tracking sector splits, now at $9.77M average and $408 per PHI record. The Change Healthcare 2024 incident at $2.45B and over 100M affected individuals set the new upper bound.

Exhibit A

Why healthcare leads every other sector

IBM 2025

Healthcare phishing breach cost sits at $9.77M average per IBM Cost of a Data Breach 2025, the fourteenth consecutive year the sector has led every other industry on per-incident cost. The structural drivers are well understood. Protected Health Information (PHI) carries higher per-record liability than any other regulated data class at $408 per record. HIPAA enforcement layers fines on top of remediation cost, with the HHS Office for Civil Rights running an active enforcement program that has produced over $140M in cumulative settlement penalties through 2024. The HHS OCR breach portal publicly lists every healthcare breach involving more than 500 individuals, producing reputation damage that does not exist in other regulated sectors. And clinical-system disruption is a patient-safety event with civil-suit exposure independent of any data loss.

The phishing-specific picture within healthcare is heavier than the cross-sector mean. Phishing is the dominant initial access vector for healthcare breaches per Verizon DBIR 2025 healthcare annex, and the typical phishing-initiated breach in healthcare pivots quickly to either credential-takeover or ransomware deployment. The 2024 Change Healthcare incident, the largest healthcare data breach on US record, traced its initial access to credentials obtained via attacker-side phishing followed by ransomware deployment by the BlackCat (ALPHV) group. UnitedHealth Group has disclosed total incident cost of approximately $2.45B and over 100M affected individuals as of October 2024.[IBM 2025 + HHS OCR + UnitedHealth Group public disclosures 2024]

Exhibit B

The Change Healthcare 2024 case

CASE FILE

On 21 February 2024, Change Healthcare (a UnitedHealth Group subsidiary that processes approximately one in three US healthcare claims) experienced a ransomware deployment by the BlackCat / ALPHV ransomware affiliate. UnitedHealth Group has publicly stated that the initial access was obtained via compromised credentials on a Citrix Remote Access portal that was not protected by multi-factor authentication. The credential-theft step preceding the credential reuse is widely believed by independent analysts to have been a phishing-initiated theft, though UnitedHealth has not confirmed the specific credential-theft mechanism in public disclosures.

The downstream impact was unprecedented in healthcare. Claims processing across substantial portions of the US healthcare system was disrupted for weeks. Pharmacies, hospitals, and individual provider practices were unable to submit insurance claims or verify patient coverage. Independent estimates from the American Medical Association and the American Hospital Association placed weekly liquidity impact on provider practices in the tens of billions of dollars at the peak of disruption. UnitedHealth ultimately advanced approximately $9B in interest-free loans to affected providers to keep practices solvent during the disruption window.

The data-loss figures are equally significant. UnitedHealth confirmed in October 2024 that over 100 million individuals had PHI affected by the breach, making it the largest healthcare-sector PHI breach in US history. HHS OCR confirmed regulatory investigation. The cost figure of $2.45B includes IR engagement, ransomware payment (UnitedHealth has confirmed paying approximately $22M to BlackCat), provider loans, notification, monitoring services, and the system rebuild. Litigation cost is still accruing as of mid-2026 with multiple class actions pending. The Change Healthcare case anchors the upper bound of modern healthcare phishing-cost analysis and demonstrates that the per-incident cost can scale to 9-figure outcomes when the affected entity sits at a healthcare-infrastructure choke point.[UnitedHealth Group Q2-Q3 2024 disclosures + HHS OCR breach portal + Senate Finance Committee hearing testimony May 2024]

Exhibit C

The HIPAA breach-notification mechanics that drive cost


Healthcare breach cost is shaped by the HIPAA Breach Notification Rule, which is structurally more aggressive than equivalent rules in other regulated sectors. Three mechanics drive cost. First, individual-notification timing: breaches involving more than 500 individuals require notification of HHS Secretary, individual notification, and prominent-media notification within 60 days of discovery. The 60-day window forces rapid forensic determination of scope and identity, which compresses the IR engagement into a higher-cost timeframe. Second, the public-listing requirement: every healthcare breach involving more than 500 individuals is listed on the public-facing OCR breach portal with entity name, individuals affected, and breach type. The portal is searchable and frequently referenced by patient-advocacy groups, journalists, and downstream litigation counsel. The reputation-damage cost is structurally embedded in the regulation. Third, the per-violation civil monetary penalty schedule: HIPAA fines run $100 to $50,000 per violation with a $1.5M annual cap per violation category, with several categories aggregating to total annual liability above $5M for serious cases.

The HHS OCR enforcement docket through 2023-2025 includes multiple seven-figure settlements driven by phishing-initiated breaches. The 2023 LifeLabs settlement (approximately $9.8M across multiple Canadian provinces, with parallel US class-action exposure) is illustrative of the cross-jurisdictional fine layering that international healthcare entities face. Smaller-entity settlements in the $250K to $2M band are routine and the enforcement cadence has been steady through the post-pandemic period.[HHS OCR enforcement annex 2023-2025 + 45 CFR 164.404-414]

Exhibit D

Cost-line build-up against the $9.77M figure


Cost lineShare of $9.77MDollar figureDriver
Notification + monitoring + credit services23%$2.25M$408 per PHI record at scale
Incident response + forensics17%$1.66M60-day HIPAA window compresses spend
Regulatory fines (HHS OCR + state)14%$1.37MHIPAA + state AG layering
Legal + class-action exposure13%$1.27MPHI exposure routine class trigger
Clinical-disruption cost11%$1.07MCancelled procedures, diverted patients
Direct ransomware / wire loss10%$977KWhere phishing pivoted to ransomware
Customer / patient churn7%$684KPatient panel shifts after disclosure
Security-control rebuild5%$489KOne-time post-event capex

The notification and clinical-disruption lines are structurally larger than for any other sector. The clinical-disruption line is the single most-overlooked cost in healthcare breach modelling because it does not appear as a discrete IT cost; it surfaces in revenue-cycle slowdown, deferred procedures, and patient-safety litigation.[IBM 2025 healthcare cohort + HHS OCR enforcement record]

Exhibit E

The clinical-disruption-as-patient-safety dimension


Healthcare phishing breach cost includes a category that does not exist meaningfully in other sectors: patient-safety liability for clinical-system disruption. When a phishing-initiated ransomware event takes down a hospital's electronic medical records, medication-ordering, lab-results, or imaging systems, the resulting clinical disruption creates patient-safety risk that has translated into documented patient deaths in multiple 2023-2024 cases. The civil-suit exposure for these deaths is independent of the data-loss exposure and is increasingly modelled as a discrete cost line.

Two reference cases anchor the patient-safety cost line. The 2019 Springhill Medical Center case in Alabama involved the documented death of a newborn whose treatment was affected by a ransomware-driven downtime of fetal monitoring. The subsequent wrongful-death suit (Kidd v. Springhill Medical Center) was the first US case to assert direct causal liability between a cyberattack-driven clinical-system outage and a patient death. The case settled in 2023 with terms undisclosed but reportedly substantial. The 2020 University Hospital Düsseldorf incident in Germany involved a patient death attributed to ambulance diversion during a ransomware-driven clinical-system outage; German prosecutors investigated but ultimately did not file homicide charges, leaving the civil exposure as the primary cost vector.

The expected trajectory is that patient-safety litigation will become a routine component of major healthcare phishing-breach cost modelling through 2026-2028. Healthcare-sector cyber insurance carriers have already begun pricing this risk into coverage exclusions and sub-limits. Hospital boards have begun explicitly factoring clinical-system continuity into cyber-investment decisions in a way that does not have a parallel in other regulated sectors. The implication for the per-incident cost figure is that the $9.77M IBM average is likely an underestimate of true cost in cases where clinical disruption was material.[Kidd v. Springhill 2019-2023 case record + Düsseldorf 2020 incident reporting]

Exhibit F

Controls: workforce MFA, third-party SLA, segmented OT


#1Phishing-resistant MFA across clinical workforce

~90% of credential-pivot value
Cost: $50 per user one-time

FIDO2 hardware-key MFA across clinical, billing, and IT-admin populations. The single most-leveraged healthcare phishing defence and the control whose absence enabled the Change Healthcare initial access.

#2MFA enforcement on every remote-access portal

~85% of remote-access-portal compromise
Cost: Platform-licence dependent

Every Citrix, RDP, VPN, and admin-portal endpoint requires MFA. The Change Healthcare remote-access portal that was compromised was not protected by MFA. Enforcing MFA portal-wide is a mandatory control by 2026 and the most-cited gap in OCR enforcement findings.

#3Network segmentation between clinical OT and IT

~60% of clinical-disruption cost
Cost: 6-18 months of network-engineering work

Segmenting clinical operational technology (medication-ordering, EHR, lab-results, imaging) from corporate IT limits the blast radius when phishing-initiated ransomware deploys. Hospital ransomware events that completed clinical-system takedown almost universally had insufficient segmentation.

#4Third-party vendor MFA SLAs in BAA contracts

~40% of vendor-pivot risk
Cost: Procurement-team work

HIPAA Business Associate Agreements should require MFA enforcement on the BA's workforce as a contractual condition. Many existing BAAs predate the modern phishing threat model and do not include MFA SLAs. Updating BAA templates is procurement-team work with high regulatory leverage.

#5Behavioural email security with healthcare-specific tuning

~50% of lure delivery
Cost: $42 to $96 per mailbox per year

Behavioural email security catches the spear-phish and BEC patterns common against healthcare finance and HR teams. Healthcare-specific tuning catches lures impersonating HHS, CMS, and major insurance carriers.

#6Clinical-continuity playbook for 7-14 day downtime

~50% of clinical-disruption cost
Cost: $50K to $250K one-time

Pre-built downtime procedures, paper-backup workflows, manual order-tracking protocols. Reduces patient-safety exposure during the days-to-weeks window before clinical systems are restored. Mandatory for any hospital system with ransomware exposure.

Exhibit G

Frequently filed questions

ON RECORD

What is the average phishing-related breach cost in healthcare?[open]

$9.77M average per IBM 2025. Highest of any sector for 14 consecutive years. Per PHI record at $408.

What did the Change Healthcare 2024 breach cost?[open]

UnitedHealth Group has disclosed approximately $2.45B in total incident cost as of late 2024, with over 100M individuals affected. The largest healthcare-sector PHI breach in US history.

What was the Change Healthcare initial access vector?[open]

UnitedHealth has publicly confirmed compromised credentials on a Citrix Remote Access portal that was not protected by MFA. The credential-theft preceding the reuse is widely believed to have been phishing-initiated.

How does HIPAA breach notification work?[open]

Breaches involving 500+ individuals require notification of HHS Secretary, individual notification, and prominent-media notification within 60 days of discovery. Breaches are also publicly listed on the HHS OCR breach portal.

Does clinical disruption count toward breach cost?[open]

Yes, including cancelled procedures, diverted ambulances, deferred surgeries, and patient-safety civil-suit exposure. Multiple 2023-2024 hospital ransomware events have included documented patient deaths attributed to clinical-system unavailability.

What is the highest-leverage control?[open]

Phishing-resistant MFA across the clinical workforce, then MFA enforcement on every remote-access portal. Both gaps are heavily-cited in OCR enforcement findings.

Are BAA contracts a meaningful control surface?[open]

Yes. Updating Business Associate Agreement templates to require MFA enforcement on the BA workforce is procurement-team work with high regulatory leverage. Many existing BAAs predate the modern phishing threat model.

Updated 2026-04-27