2024 · 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
Expertise to Execution
Evidence coverage: 3/6 stages, weight 19/60
Decisive stage: detection (clearest evidence) · Alternative: Strategy to Execution
(1) Strategic expectation: as the 62-bed acute-care hospital serving western Oklahoma, Great Plains Regional Medical Center holds protected health information for much of its region's population and is expected to detect an intrusion before encryption begins, to notice or interrupt bulk copying of patient records, and to keep those records recoverable. (2) In practice: an unknown actor was inside the network from 5 September 2024 and it surfaced only on 8 September when the ransomware was deployed; before encrypting, the actor copied files containing the PHI of 133,149 individuals, which the hospital learned of only through the subsequent forensic investigation; systems were restored quickly, but a limited amount of patient information was never recoverable. The entry vector was never disclosed and no group claimed responsibility, so neither is load-bearing. (3) The gap sits in the material column: detection, egress monitoring and backup coverage are known technical remedies owned by technical operations, and no source documents a formal artefact that failed to translate or a leadership decision that deferred, underfunded or accepted the gap; the organisation simply did not realise available detective controls in operations, so the interaction of knowing and doing is an Expertise to Execution gap. The classification rests on the detection stage (clearest evidence: a documented ~3-day dwell time ending at encryption), corroborated by the egress stage of the same type; the recovery stage shows a secondary, weaker Strategy to Execution pattern. RM34 (Expertise to Execution lens): the available detection tooling and alert handling were insufficiently configured or staffed to catch activity that ran for three days before declaring itself through encryption, so the intrusion stayed hidden while data was staged and copied (causal role: Obscuring). RM35 (Expertise to Execution lens): bulk copying of protected health information left the network undetected and uninterrupted, and was established only after the fact by the forensic firm, so the egress visibility a PHI estate requires was not realised in operations (causal role: Amplifying). RM31 (Expertise to Execution lens): the restore covered almost everything but a limited amount of patient information was not recoverable, so backup coverage was not fully built out for the record estate despite the fast overall recovery (causal role: Constraining).
RM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapRM31 — Resilience / backup preparedness gapEuRepoC row; victim, country (United States) and year (2024, start_date 05.09.2024) taken from the case file and confirmed by the victim's own notice. Description matches the stated victim. Entry vector undisclosed, actor unattributed and no ransomware group claimed responsibility; whether a ransom demand was made or paid was not disclosed, so no extortion-governance conclusion is drawn. HHS/OCR reporting date varies across sources (Healthcare Infosecurity says 7 November 2024; the EuRepoC row carries 19 November 2024, the date the filing became public); both fall inside the HIPAA 60-day window from the 8 September discovery, so no disclosure failure is coded. The Murphy Law Firm press release calling the environment inadequately secured is a plaintiff-side claim and is not used as evidence. The victim's notice URL works without a trailing slash (https://gprmc-ok.com/notice-of-security-incident); the trailing-slash variant in the case file returned an HTTP error. No related_rows in the case file. Link check: gprmc-ok.com blocks automated access (HTTP 403); the page was opened and read during research.