2023 · United States · Q - Human health and social work activities · Data theft via network intrusion
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via network intrusion
Strategy to Leadership
Evidence coverage: 3/6 stages, weight 20/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Leadership
(1) Strategic expectation: Sav-Rx is a HIPAA-regulated pharmacy benefit manager holding Social Security numbers and health-related records for nearly 2.8 million participants; the doctrinal column was explicit - HIPAA obligations to safeguard and monitor that data, and the company's own Notice of Privacy Practices promising to let individuals know promptly if a breach occurs. (2) In practice: an intruder was inside from 3 to 8 October 2023 and took files from non-clinical systems undetected; the company noticed only a network interruption; the core operational recovery worked (restored next business day, no pharmacy impact); but individuals were not notified until 10 May 2024 and HHS until 24 May 2024, roughly seven months after the company knew health-information files had been taken - a delay it publicly attributed to prioritising patient care and a deliberately unhurried investigation. The post-incident remediation list (first 24/7 SOC, MFA on critical accounts, network segmentation, patching cycle, monitoring) shows several basic controls had not been stood up before the breach. (3) That is a knowing-doing gap inside the doctrinal column: the commitments existed and were accurate on paper, but leadership did not translate them into decisions - the detection and egress capabilities were never commissioned beforehand (built only after the fact), and the notification timeline was set at the decision level contrary to the rule and the company's own public promise. The classification rests on the response/disclosure stage, the best-documented one (the victim's own filings); the entry vector was never disclosed and is not load-bearing. RM34 (Strategy to Leadership lens): leadership oversight never put a detection objective in place - a five-day dwell ended only in an accidental network interruption, and the SOC and monitoring tools appear on the remediation list only after the incident, so the intrusion stayed hidden while data was taken (causal role: Obscuring). RM35 (Strategy to Leadership lens): exfiltration of the records of 2,812,336 people left the network between 3 and 8 October 2023 without strategic attention to egress risk - no outbound-visibility control existed to interrupt it, and the scale of the exposure is the direct measure of that absence (causal role: Amplifying). RM39 (Strategy to Leadership lens): disclosure behaviour diverged from the strategic commitment - the company's own privacy notice promised prompt notice and HIPAA sets a 60-day outer limit from discovery, yet individuals were told about seven months after the company knew health-information files had been taken (causal role: Constraining).
RM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapRM39 — Breach notification / disclosure failureVictim is given as 'SAV-RX' in the case file (receiver_name); the operating entity is A&A Services, LLC d/b/a Sav-Rx, a family-owned PBM in Fremont, Nebraska. The live Maine AG notification URL in the case file returns HTTP 404; the archived snapshot actually read is cited instead. The Maine filing records 'Date Breach Discovered: 04/30/2024' while the company's own notice says it identified the network interruption on 8 October 2023 and knew then that files containing health information had been obtained; the RM39 reading of an unreasonable delay rests on the October 2023 knowledge, and the company's later 'discovery' framing is recorded as the open question behind the primary-open source type. Whether a ransom was paid was never confirmed; the company's statement that acquired data was 'destroyed and not further disseminated' led quoted analysts to suspect negotiation (GovInfoSecurity, 29 May 2024); the incident was not yet on the HHS OCR breach portal at that date. The class-action plaintiffs allege the data was held unencrypted and that HIPAA/FTC-standard safeguards were missing; the court (Prestby et al., D. Neb. 8:24-cv-00204, order of 5 January 2026) ruled only on motions to dismiss - the negligence claim proceeds - so no court or regulator finding on the safeguards exists and RM26/RM03 were not coded. Entry vector and actor never disclosed. Related row 797 (informationisbeautiful) describes the same incident per its title, but its case file row-797.json is not in cases-run500 and no result-797.json exists in the output directory, so no cross-check was possible. Link check: hhs.gov blocks automated access (HTTP 403); the page was opened and read during research.