2023 · United States · Q - Human health and social work activities · Ransomware attack with data theft
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with data theft
Strategy to Execution
Evidence coverage: 2/6 stages, weight 14/60
Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution
(1) Atlantic General Hospital, a not-for-profit rural hospital and HIPAA-covered entity, sat under regulatory and contractual expectations (the HIPAA regime, insurer underwriting the CEO cited, its own privacy notice) to know where its sensitive patient and employee data sat, to protect it, and to detect intrusions. (2) In practice, unauthorized access ran Jan 20-29 2023 unnoticed and was discovered only when ransomware encryption disrupted services; attackers reached internal folders and files holding employee and patient data; and the hospital's own scoping failed - the initial review (completed Mar 6, notified Mar 24) counted 30,407 affected individuals, while further investigation completed May 15 2023 found additional compromised files and raised the total 4.5-fold to 136,981, forcing a second notification wave on Jun 22. (3) The classification rests on the egress/data-governance stage: the expectation was doctrinal (regulatory obligations and the hospital's own committed privacy policies and procedures), and the chain broke in execution - those obligations were not operationalised in systems and data inventories, so the organisation did not accurately know its own sensitive-data holdings and exposed more records than its first accounting held, a knowing-doing gap between formal obligations and operational reality rather than generic weak security. The entry vector was never disclosed and is not load-bearing. The 9-day dwell is a real second pattern (Expertise to Execution via the detection gap), but no source documents the hospital's monitoring setup, so it is recorded as a stage, not the decisive one. RM16 (Strategy to Execution lens): the hospital's data-classification and privacy obligations were not implemented in its systems and processes - a completed scoping review missed roughly 106,000 individuals' records that sat in additional compromised files, so far more data was exposed than its own accounting acknowledged (causal role: Amplifying). RM34 (Strategy to Execution lens): monitoring and alert-handling requirements were not operated as intended - the intrusion persisted for nine days and surfaced only through the impact of encryption, obscuring both the access and the data exposure while it ran (causal role: Obscuring). RM15 (Strategy to Execution lens): data-flow and asset visibility requirements were not reflected in inventories - forensic scoping had to be reopened because more affected files were discovered only after the first review was declared complete (causal role: Enabling).
RM16 — Data governance / minimisation gapRM34 — Monitoring / detection / alert-handling gapRM15 — Asset / exposure visibility gapEuRepoC row; description matches the stated victim. Actor not officially attributed: the CEO said he learned through the government investigation that a ransomware group in China carried it out; kept as reported, not confirmed. Whether data was exfiltrated was never confirmed (the hospital did not answer that question; notices say information was accessed or acquired) - so no egress-monitoring marker is coded. The class action alleged unencrypted sensitive data and negligence; it settled for $2.25M (preliminary, Aug 2024) with no admission of wrongdoing and no mandated security improvements, so those allegations are not coded as established gaps. No HHS OCR enforcement action was found. The Maine AG filing records the discovery date as 03/06/2023 - the date the affected files were found to contain protected information; file encryption itself was discovered Jan 29, 2023. The Maine notice PDF linked from the filing did not load (HTTP 404); the filing's HTML summary was used instead. Link check: octodaydispatch.com blocks automated access (HTTP 429); the page was opened and read during research. Link check: healthcareitnews.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: beckershospitalreview.com blocks automated access (HTTP 403); the page was opened and read during research. The Maine AG filing and the hospital's notice page returned 404 to the automated link checker but were live when opened during research; both are cited via web.archive.org snapshots opened and read during this task.