Publication note: This teardown preserves the supplied research and its evidence labels. Historical and regulatory statements reflect that research cutoff, not a fresh verification at publication. Control mappings are illustrative, not findings of ISO/IEC 27001 nonconformity. Kit document names and reference codes in the source are illustrative labels and may differ from the current catalog; documentation alone is not evidence of an operating control. Financial caveat: The source gives differing provider-advance amounts and labels its interim $2.457 billion figure as direct cost while its full-year $2.223 billion direct-cost figure is lower. Those classifications are not reconciled here. Do not add interim and full-year figures, ransom, advances or later charges into a new total. The approximately $22 million ransom amount is reported; acknowledgment of payment does not independently confirm that amount.
Executive Overview
On February 21, 2024, UHG detected ransomware inside Change Healthcare—systems processing roughly 15 billion transactions annually covering approximately one-third of U.S. patient records. The result: 192.7 million individuals exposed, the largest U.S. healthcare data breach on record, weeks of nationwide claims-processing disruption, and continuing congressional oversight, an open HHS OCR investigation, multidistrict litigation, and state enforcement. This autopsy examines the timeline, regulatory response, financial costs, ISO/IEC 27001:2022 control gaps, and how Blueprint by Aegora's free kit addresses each structural failure, distinguishing confirmed facts, reported claims, and analytical inferences throughout.
1. Incident Timeline and What Happened
February 12, 2024 — Initial Access: Threat actors used compromised credentials to access a Change Healthcare Citrix portal lacking MFA. CEO Andrew Witty acknowledged this in testimony before the Senate Finance Committee and House Energy and Commerce Subcommittee on May 1, 2024; no formal HHS OCR finding has independently confirmed it. Over nine days, attackers moved laterally and exfiltrated ~4–6 terabytes—including PHI, insurance details, billing records, Social Security numbers, and financial identifiers.
February 21, 2024 — Detection and Containment: Ransomware was deployed; UHG disconnected Change Healthcare, halting claims processing, payment disbursements, eligibility verifications, and e-prescribing nationwide; UHG filed an SEC Form 8-K February 22, 2024. An AHA survey of nearly 1,000 hospitals found 94% experienced financial repercussions and 74% direct patient care impacts; some providers furloughed staff or took personal loans to stay operational.
March 2024 — Phased Restoration: By March 7, 99% of pharmacy services were restored; electronic payments followed March 15 and medical claims connectivity March 18. By April 22, ~80% of functionality was restored; full restoration of secondary tools extended through late 2024.
March–April 2024 — Ransom and Secondary Extortion: UHG paid approximately $22 million in Bitcoin to ALPHV/BlackCat. ALPHV conducted an exit scam—keeping the ransom without paying its affiliate or deleting the data. That affiliate joined RansomHub, launched a secondary extortion campaign, and leaked patient data in April 2024. No confirmed second UHG payment to RansomHub appears in reviewed sources.
July 19, 2024: Change Healthcare filed its breach report with HHS OCR, listing ~500 individuals as a preliminary placeholder.
July 31, 2025: Change Healthcare reported 192.7 million individuals affected—the largest healthcare data breach in U.S. history.
Public sources reviewed do not verify that UHG or Change Healthcare held ISO/IEC 27001 certification at the time of the incident.
2. Enforcement and Regulatory Response
HHS OCR Investigation
HHS OCR opened a proactive HIPAA compliance investigation examining the Privacy, Security, and Breach Notification Rules. As of October 15, 2026, no settlement, civil monetary penalty, or resolution agreement has been confirmed; the investigation remains active. OCR has emphasised that active implementation, documented risk management, and testing—not written policies alone—demonstrate compliance.
HIPAA Security Rule Proposed Rulemaking
On January 6, 2025, HHS published an NPRM—"HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information" (90 FR 898, document 2024-30983)—the most comprehensive proposed Security Rule update since 2013. The comment period closed March 7, 2025 (~4,745 comments); the rule remains unfinalized, with a projected final date of July 2027. Key proposals include mandatory MFA, ePHI encryption at rest and in transit, network segmentation, semi-annual vulnerability scanning, annual penetration testing, annual written verification of business associate technical safeguards, and elimination of the "addressable" category. A coalition of over 100 healthcare organisations petitioned HHS in December 2025 to withdraw the proposal, citing estimated first-year costs of ~$9 billion; the NPRM is not final law as of October 15, 2026.
CMS Emergency Accelerated Payments (CHOPD Program)
CMS launched the CHOPD Accelerated and Advance Payment program in early March 2024, disbursing over $2.55 billion to more than 4,200 Part A providers and ~$717 million to over 4,700 Part B suppliers. Repayment occurred via automatic recoupment at 100% of incoming Medicare claims; CMS stopped accepting applications July 12, 2024, recovering more than 96% of funds by June 2024. These are recoupable advances, not sunk costs.
Congressional Oversight
CEO Witty testified before the Senate Finance Committee and House Energy and Commerce Subcommittee on May 1, 2024. Senator Ron Wyden characterised the absent MFA as "cybersecurity 101"; legislators also pressed on UHG's market dominance and systemic risk. Witty acknowledged he could not guarantee attackers would not release further data. New CEO Stephen Hemsley testified at a House hearing on healthcare consolidation on January 22, 2026.
Litigation
Class-action suits consolidated into MDL No. 3108, U.S. District Court for the District of Minnesota, before Judge Donovan W. Frank. On December 19, 2025, the court denied motions to dismiss negligence, consumer protection, and health record privacy claims. As of October 2026, no global settlement has been finalized and no claim forms distributed. Nebraska's AG filed suit in December 2024, surviving a motion to dismiss in November 2025; Iowa's AG filed in March 2026 alleging consumer fraud and data breach violations. A coalition of 22 state AGs sent a joint letter in 2024 reserving future enforcement rights.
3. Financial Analysis
The financial picture demands careful disaggregation: provider advances and CMS CHOPD disbursements are recoupable—not unrecoverable losses—and must not be aggregated into direct breach costs; each category is presented with source attribution and confirmation status.
| Category | Amount | Currency | Source | Status |
|---|---|---|---|---|
| Ransom paid to ALPHV/BlackCat (Bitcoin, ~March 2024) | ~$22 million | USD | CEO Witty, Congressional testimony | Payment acknowledged in testimony; approximate amount reported, not independently confirmed here |
| UHG direct response costs — full year 2024 | ~$2.223 billion | USD | UHG SEC filings | Reported per SEC filings |
| UHG business disruption costs — full year 2024 | ~$867 million | USD | UHG SEC filings | Reported per SEC filings |
| Total UHG cyberattack financial impact, 2024 (direct + disruption) | ~$3.09 billion | USD | UHG SEC filings | Reported per SEC filings |
| Interim Q3 2024 total direct cost (through Sept 30, 2024) | ~$2.457 billion | USD | UHG Q3 2024 reporting | Reported per SEC filings; superseded by full-year figure above |
| Final cyberattack costs recognised in Q4 2025 (reported Jan 2026) | $799 million | USD | UHG earnings release, Jan 27, 2026 | Confirmed in SEC filing |
| UHG Temporary Funding Assistance — provider advances/interest-free loans | >$6.5 billion (as of May 2024 testimony); up to $9 billion in some reporting | USD | Witty testimony; company updates; secondary reporting | Reported; recoupable advances, excluded from direct breach costs |
| CMS CHOPD — Medicare accelerated payments (Part A + Part B) | ~$3.27 billion | USD | CMS official data | Confirmed by CMS; 96%+ recovered June 2024; government programme, not UHG cost |
| RansomHub secondary extortion demand | Not quantified | — | Reputable reporting | Reported; no confirmed second payment by UHG |
Exclusions and caveats: Provider advances and CMS disbursements are recoupable liquidity programmes, not direct incident costs. The $22M ransom is incorporated in the 2024 cost figure; ALPHV's exit scam yielded no data-security benefit. Provider advance totals vary: testimony confirmed over $7 billion; some reports cite up to $9 billion. Insurance recovery amounts are undisclosed in public SEC filings.
4. ISO/IEC 27001:2022 Annex A Control Mapping
The table maps incident observations to ISO/IEC 27001:2022 Annex A controls. "Confirmed" = primary-source support; "Analytical inference" = logical deductions from confirmed facts not independently stated by any authoritative source.
| Control ID | Control Title | Failure / Observation | Evidence Status | Limit |
|---|---|---|---|---|
| A.8.5 | Secure authentication | Citrix portal lacked MFA; compromised credentials provided initial entry | Confirmed in testimony | Limit: A.8.5 reduces credential-based initial access risk but does not eliminate phishing, SIM-swapping, or authenticator-bypass threats even when MFA is deployed. |
| A.8.2 | Privileged access rights | Nine-day lateral movement suggests overly broad post-authentication access privileges | Analytical inference | Limit: A.8.2 reduces exploitable access scope but does not prevent lateral movement if privilege review cadences are insufficient or network trust boundaries are inadequately enforced. |
| A.8.8 | Management of technical vulnerabilities | Legacy Citrix portal lacked current controls; post-acquisition infrastructure modernisation remained underway at breach time | Reported | Limit: A.8.8 reduces exploitation of known vulnerabilities but cannot close gaps in inherited infrastructure not yet assessed or remediated under the acquiring entity's standards. |
| A.8.13 | Information backup | Weeks-to-months restoration timelines indicate backup architectures insufficient for rapid recovery | Analytical inference | Limit: A.8.13 reduces data loss risk but recovery speed depends on backup frequency, offline/offsite architecture, and restoration testing the control does not mandate. |
| A.5.30 | ICT readiness for business continuity | Nationwide outage persisted for weeks; 94% of hospitals reported financial impact | Confirmed (impact) / Analytical inference (control gap) | Limit: A.5.30 reduces continuity failure duration but requires tested plans, realistic RTOs, and pre-validated alternative processing arrangements to be effective. |
| A.8.16 | Monitoring activities | Nine-day dwell time before detection signals insufficient anomaly detection or alert escalation | Analytical inference | Limit: A.8.16 reduces dwell time through active monitoring but cannot guarantee detection without appropriate baselines, tuned alerting, and continuously staffed response capability. |
| A.8.15 | Logging | Nine-day undetected lateral movement indicates inadequate logging coverage or active log review | Analytical inference | Limit: A.8.15 reduces forensic gaps and supports detection but is effective only when logs are actively reviewed, retained appropriately, and correlated across system boundaries. |
| A.8.22 | Segregation of networks | Attackers moved laterally from the Citrix entry point across the network over nine days | Analytical inference | Limit: A.8.22 reduces the blast radius of an initial compromise but cannot fully contain a determined attacker with valid credentials if segmentation is insufficiently granular. |
| A.8.7 | Protection against malware | ALPHV/BlackCat ransomware deployed and encrypted systems; no evidence of pre-execution interception | Analytical inference | Limit: A.8.7 reduces malware execution risk but cannot prevent all ransomware variants, including those using living-off-the-land techniques or signed binaries to evade detection. |
| A.5.24 | Information security incident management planning and preparation | Scale and duration of disruption indicate IR planning did not anticipate a total clearinghouse failure scenario | Analytical inference | Limit: A.5.24 improves preparedness and shortens mean time to respond but does not guarantee resilience against novel large-scale incidents not previously modelled. |
| A.5.25 | Assessment and decision on information security events | Nine-day dwell time before escalation indicates event triage thresholds failed to trigger timely investigation | Analytical inference | Limit: A.5.25 improves speed of event classification and escalation but requires reliable telemetry, pre-defined thresholds, and trained analysts to function effectively. |
| A.5.26 | Response to information security incidents | Weeks of restoration combined with secondary RansomHub extortion highlight gaps in post-breach response and communication | Reported | Limit: A.5.26 structures incident response but effectiveness depends on exercised playbooks, clear authority chains, and coordinated supplier engagement not ensured by documentation alone. |
| A.5.23 | Information security for use of cloud services | Cloud and remote-access infrastructure security requirements were not formally embedded in agreements or configurations | Analytical inference | Limit: A.5.23 formalises cloud security obligations but reduces risk only when requirements are actively verified in supplier contracts and periodically tested in production. |
| A.5.19–A.5.22 | Supplier relationship controls (Information security in supplier relationships; Addressing security within supplier agreements; ICT supply chain; Monitoring and review of supplier services) | Change Healthcare acquired 2022; legacy security posture not fully uplifted to UHG standards before the 2024 breach | Reported | Limit: A.5.19–A.5.22 reduce supplier-introduced risk through contractual obligations and ongoing monitoring but cannot eliminate inherited vulnerabilities where integration timelines extend for years without compensating controls. |
5. What Blueprint by Aegora's Free Kit Would Have Addressed
Blueprint by Aegora is a free ISO/IEC 27001:2022 documentation kit of 109 Auditor-Ready Documents (aegoragrc.com). The table maps principal risk themes to specific kit documents. A rigorously implemented and tested ISMS reduces risk and improves response speed—it does not guarantee prevention of a sophisticated ransomware actor but provides the structural foundation for an operational security culture.
| Risk Theme from Incident | Blueprint Kit Documents | Document IDs |
|---|---|---|
| MFA absent on remote-access portal; stolen credentials as root cause | Access Control Policy; Access Control Procedure; Password Management Policy; Password Management Procedure | AEG-POL-002; AEG-PRC-001; AEG-POL-024; AEG-PRC-016 |
| Nine-day dwell time; absent structured IR escalation and containment protocols | Incident Management Policy; Incident Response Plan; Incident Response Playbooks; Incident Log | AEG-POL-018; AEG-PRC-009; AEG-PRC-010; AEG-REG-008 |
| Extended restoration timelines; backup capability insufficient for rapid recovery | Backup & Retention Policy; Backup & Retention Procedure | AEG-POL-005; AEG-PRC-004 |
| Nationwide continuity failure; untested BCDR for a total clearinghouse outage | Business Continuity Policy; Business Continuity Plan; Business Impact Assessment Register | AEG-POL-006; AEG-PRC-005; AEG-REG-002 |
| Nine-day lateral movement without log-based detection or alert escalation | Logging and Monitoring Policy; Logging and Monitoring Procedure | AEG-POL-021; AEG-PRC-013 |
| Lateral movement from Citrix entry point across a flat network | Network Security Policy; Network Security Procedure | AEG-POL-023; AEG-PRC-015 |
| Legacy Citrix infrastructure unpatched; security posture not uplifted post-acquisition | Vulnerability Management Policy; Patch Management Policy; Patch Management Procedure; Vulnerability Management Procedure | AEG-POL-035; AEG-POL-025; AEG-PRC-017; AEG-PRC-022 |
| ALPHV/BlackCat a known active threat actor; no evidence of proactive threat-intelligence use | Threat Intelligence Policy; Threat Intelligence Procedure | AEG-POL-034; AEG-PRC-021 |
| Cloud and remote-access security obligations not formally embedded | Cloud Security Policy | AEG-POL-009 |
| Legacy security posture inherited at acquisition; no documented ongoing supplier security uplift | Supplier Relationship Policy; Supplier Relationship Procedure; Master Service Agreement Template; Supplier Due Diligence Checklist; Vendor Matrix | AEG-POL-031; AEG-PRC-020; AEG-TPL-005; AEG-TPL-009; AEG-REG-019 |
| Absent risk-based ISMS scope, asset inventory, and security role accountability | Risk Register; Statement of Applicability; Asset Register; ISMS Manual; Roles & Responsibilities Document | AEG-REG-016; AEG-REG-017; AEG-REG-001; AEG-POL-017; AEG-POL-030 |
The kit gives compliance officers, CISOs, and IT managers a documented starting point for a functioning ISMS. It is not a substitute for executive commitment, skilled personnel, and regular testing—documentation is the layer that makes everything else verifiable.
6. Key Takeaways
- MFA on every remote-access entry point is non-negotiable. The breach originated from a Citrix portal without MFA—now proposed as mandatory in the HIPAA Security Rule NPRM and identified universally as the foundational control failure.
- Network segmentation contains blast radius. Nine-day lateral movement through a flat network demonstrates the cost of insufficient segmentation. Documented, enforced segmentation (A.8.22) is essential wherever remote-access entry points exist.
- Test backups and continuity plans before you need them. Weeks of nationwide outage reflect an untested continuity design for total-clearinghouse failure. BIAs must map RTOs to real infrastructure dependencies and be exercised annually against realistic failure modes.
- Supplier and acquisition risk management must be proactive and sustained. Change Healthcare's legacy posture—inherited at the 2022 acquisition but not uplifted before the breach—shows due diligence cannot end at deal close. Requirements must be in contracts, verified regularly, and supported by compensating controls during integration.
- Ransom payment is not a recovery strategy. The $22 million paid to ALPHV/BlackCat did not secure data deletion or end extortion—the affiliate launched a secondary RansomHub campaign. Ransom funds criminal infrastructure and provides no enforceable guarantee of data destruction.
- Incident response requires practiced playbooks, not just written policies. The disruption and secondary extortion demonstrate underprepared IR programmes fail under pressure. Playbooks must cover ransomware scenarios, notification chains, regulatory communication, and provider-facing crisis response.
- Regulatory exposure is now multi-jurisdictional and expanding. OCR's investigation remains open; MDL litigation continues without settlement; two state AGs have filed suit. The HIPAA NPRM, if finalised, would mandate MFA, segmentation, and annual testing. Treat regulatory risk as dynamic, not a fixed checklist.
7. Methodology and Limitations
Evidence labelling: "Confirmed" = primary sources (SEC filings, testimony, CMS/HHS publications, official statements). "Reported" = reputable secondary coverage without a contradicting primary source. "Analytical inference" = logical deductions not independently stated by any authoritative source. These labels govern claim weighting throughout.
Record cutoff: Facts, regulatory status, and litigation status assessed as of October 15, 2026.
ISO/IEC 27001 certification status: Public sources do not verify that UHG or Change Healthcare held ISO/IEC 27001 certification at the time of the breach.
Financial figures: UHG cost figures from SEC filings and congressional testimony; provider advance totals vary; insurance recovery amounts are undisclosed in public SEC filings.
Regulatory mappings: HIPAA and ISO/IEC 27001:2022 Annex A references are indicative analytical mappings only. Implementing these controls does not constitute HIPAA compliance or satisfy any specific legal obligation—these mappings are a risk-management thinking tool, not legal advice.
*Blueprint by Aegora provides a complete, free ISO/IEC 27001:2022 documentation kit — 109 Auditor-Ready Documents covering policies, procedures, registers, and templates across every major ISMS domain. Access the full kit and book a complimentary consultation at aegoragrc.com.*
Sources
- https://hyperproof.io/resource/understanding-the-change-healthcare-breach/ (published 2026-08-10)
- https://energycommerce.house.gov/posts/what-we-learned-change-healthcare-cyber-attack
- https://www.hipaajournal.com/change-healthcare-responding-to-cyberattack/ (published 2025-11-17)
- https://www.hhs.gov/hipaa/for-professionals/special-topics/change-healthcare-cybersecurity-incident-frequently-asked-questions/index.html (published 2025-08-13)
- https://www.cybersecuritydive.com/news/unitedhealth-change-attack-tech-takeaways/715200/ (published 2024-05-06)
- https://www.congress.gov/118/meeting/house/117242/witnesses/HHRG-118-IF02-Wstate-WittyS-20240501-SD005.pdf (published 2024-05-13)
- https://www.infosecurity-magazine.com/news/unitedhealth-breach-stolen/ (published 2024-05-01)
- https://www.healthcaredive.com/news/change-healthcare-compromised-credentials-no-mfa/714824/ (published 2024-04-30)
- https://www.finance.senate.gov/hearings/hacking-americas-health-care-assessing-the-change-healthcare-cyber-attack-and-whats-next
- https://www.congress.gov/118/chrg/CHRG-118shrg63595/CHRG-118shrg63595.pdf
- https://www.security.org/identity-theft/breach/change-healthcare/ (published 2026-07-08)
- https://www.hipaaguide.net/change-healthcare-data-breach/ (published 2025-08-07)
- https://www.healthcaredive.com/news/change-healthcare-cyberattack-congress-unitedhealth-andrew-witty/714954/ (published 2024-05-02)
- https://www.congress.gov/118/meeting/house/117150/documents/HHRG-118-IF14-Transcript-20240416.pdf (published 2024-04-16)
- https://www.sec.gov/Archives/edgar/data/731766/000073176624000045/0000731766-24-000045-index.htm (published 2024-02-22)
- https://www.aha.org/change-healthcare-cyberattack-underscores-urgent-need-strengthen-cyber-preparedness-individual-health-care-organizations-and
- https://d1dth6e84htgma.cloudfront.net/Public_Memo_OI_Hearing_05_01_24_Change_Healthcare_Cyberattack_6a53b333f6.pdf
- https://www.unitedhealthgroup.com/newsroom/2024/2024-03-07-uhg-update-change-healthcare-cyberattack.html (published 2024-03-08)
- https://www.unitedhealthgroup.com/newsroom/2024/2024-03-18-uhg-cyberattack-status-update.html (published 2024-03-18)
- https://www.sec.gov/Archives/edgar/data/731766/000073176624000150/pressreleasedatedapril2220.htm (published 2024-04-22)
- https://www.congress.gov/crs-product/IN12330
- https://www.kaspersky.com/blog/unitedhealth-ransomware-attack/53065/ (published 2025-02-20)
- https://www.talli.ai/blog/change-healthcare-data-breach-settlement (published 2026-02-23)
- https://www.hhs.gov/about/news/2024/05/31/ocr-updates-change-healthcare-cybersecurity-incident-faqs.html (published 2024-06-04)
- https://ocrportal.hhs.gov/ocr/breach/breach_report.jsf (published 2026-10-13)
- https://clearwatersecurity.com/blog/hipaa-security-rule-enforcement-2026/ (published 2026-07-09)
- https://www.hhs.gov/sites/default/files/cyberattack-change-healthcare.pdf
- https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information (published 2025-01-06)
- https://public-inspection.federalregister.gov/2024-30983.pdf
- https://compliancy-group.com/proposed-hipaa-security-rule-update-2026/ (published 2026-09-20)
- https://medcurity.com/hipaa-security-rule-2026-update/ (published 2026-10-13)
- https://www.hipaajournal.com/new-hipaa-regulations/ (published 2026-08-10)
- https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html (published 2024-12-27)
- https://www.cms.gov/newsroom/press-releases/cms-preparing-close-program-addressed-medicare-funding-issues-resulting-change-healthcare-cyber (published 2026-03-03)
- https://www.cms.gov/newsroom/fact-sheets/change-healthcare-optum-payment-disruption-chopd-accelerated-advance-payments-part-providers-part-b (published 2026-03-03)
- https://www.congress.gov/118/meeting/house/117242/witnesses/HHRG-118-IF02-Wstate-WittyS-20240501.pdf (published 2024-04-30)
- https://www.finance.senate.gov/chairmans-news/wyden-hearing-statement-on-change-healthcare-cyberattack-and-unitedhealth-groups-response (published 2024-05-01)
- https://www.congress.gov/event/119th-congress/house-event/118890
- https://www.congress.gov/event/119th-congress/house-event/118887
- https://legalclarity.org/cybersecurity-lawsuit-news-settlements-breaches-enforcement/ (published 2026-06-22)
- https://www.mnd.uscourts.gov/content/change-healthcare-inc-data-breach
- https://settlementinsight.com/change-healthcare-data-breach-lawsuit (published 2026-10-06)
- https://www.govinfosecurity.com/state-ag-sues-change-healthcare-in-2024-ransomware-attack-a-31326 (published 2026-04-01)
- https://www.fmglaw.com/medical/strengthening-data-privacy-in-healthcare-22-state-attorneys-general-call-for-action-post-cyberattack/ (published 2024-05-28)
- https://ocsecurityaudit.com/change-healthcare-ransomware-attack-lessons/ (published 2026-10-04)
- https://www.sec.gov/Archives/edgar/data/731766/000073176626000025/a991unherq42025.htm (published 2026-01-27)
- https://www.sec.gov/Archives/edgar/data/731766/000073176626000025/q42025er992.htm
- https://www.finance.senate.gov/imo/media/doc/0501_witty_testimony.pdf (published 2024-05-01)
- https://www.sec.gov/Archives/edgar/data/731766/000073176624000146/a2024q1exhibit991.htm
- https://www.swif.ai/blog/healthcare-cybersecurity-statistics
- https://rottenwifi.com/how-the-change-healthcare-ransomware-attack-went-down-a-timeline/ (published 2026-08-10)
- https://www.moraph.com/insights/why-change-healthcare-missing-mfa-was-an-integration-failure (published 2026-10-13)