2014 · United States · Q - Human health and social work activities · Data theft via spear-phishing intrusion and APT dwell in an enterprise data warehouse
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via spear-phishing intrusion and APT dwell in an enterprise data warehouse
Strategy to Execution
Evidence coverage: 5/6 stages, weight 45/60
Decisive stage: detection (tie-break: pre-breach condition) · Alternative: Expertise to Execution
(1) Anthem, the second-largest US health insurer, held electronic protected health information on roughly 79 million people; before the intrusion the HIPAA Security Rule already obliged it to run an enterprise-wide risk analysis, to maintain procedures for regularly reviewing information system activity, and to enforce minimum access controls - a fully doctrinal expectation, reinforced by Anthem's own public commitment (its CEO wrote that the company was working around the clock to further secure member data). (2) In practice a China-based group entered through spear-phishing emails at an Anthem subsidiary (February 2014), moved from that foothold to the internally-hosted enterprise data warehouse because access to the systems holding sensitive data was not limited, reconnoitred the warehouse through late 2014, and between 2 December 2014 and 27 January 2015 staged the records of 78.8 million people into encrypted archives and transferred them to China undetected; Anthem found the intrusion itself only on 29 January 2015, about eleven months after the attack began. Regulators later documented the operational reality behind that dwell time: no enterprise-wide risk analysis ever conducted, insufficient procedures to review system activity, failure to identify and respond to suspected or known incidents, inadequate minimum access controls, unprotected credentials, un-updated security tools and inadequate logging and monitoring. (3) That is a doctrinal-material gap, not merely weak security: the obligations and even procedures existed at the strategic/ compliance level but never materialised as working monitoring, access control and egress protection in day-to-day operations, so a known-technique, patient APT could sit inside for eleven months and walk out with the crown-jewel database; the break lies in execution because no source shows the controls were decided and resourced yet not delivered, and none shows leadership deferring a documented warning. The entry vector (spear-phishing) is documented but not load-bearing for the type; the classification rests on the detection stage, which won the tie-break over the Expertise to Execution reading of the entry/containment credential gaps as the documented pre-breach structural condition, and over the Strategy to Leadership reading of the notification stage as a pre-breach condition beats a post-breach one. A secondary Strategy to Leadership pattern is visible in the response: over 50 million individuals still unnotified six weeks after disclosure, and the 2020 multistate injunction's bar on misrepresenting Anthem's security protections. (4) RM34 (Strategy to Execution lens): monitoring and alert-handling requirements were never implemented or operated as intended - the enterprise-wide risk analysis was never done and activity-review procedures were insufficient, leaving an APT undetected for roughly eleven months (causal role: Obscuring). RM35 (Strategy to Execution lens): egress controls and DLP were not translated into effective operational barriers - encrypted archive files containing 78.8 million records left the network toward China through multiple hops without detection, and the settlement later forced Anthem to build data-loss-prevention technology (causal role: Amplifying). RM30 (Strategy to Execution lens): isolation and access-limitation requirements were not implemented in architecture - access to the computers holding the sensitive data was not limited, so a phishing foothold at a subsidiary reached the central data warehouse (causal role: Amplifying). RM03 (Strategy to Execution lens): the pre-existing HIPAA Security Rule obligations were recognised at policy level but not translated into the controls, evidence or processes needed to comply - the basis of OCR's record $16 million finding (causal role: Predisposing).
RM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapRM30 — Segmentation / containment weaknessRM03 — Regulatory / stakeholder obligation gapinformationisbeautiful row: the one-sentence description matches the stated victim (Anthem, names/dates of birth/SSNs/addresses/employment data), no data-quality mismatch. incident_id not carried by the case file, left null; case file has no related_rows and no earlier Anthem result exists in the output directory. Year set to 2014, the first year of the incident (intrusion from February 18, 2014 per the OCR press release and the DOJ indictment); public disclosure was February 2015. The original hhs.gov press-release URL now redirects to a Pagefreezer archive viewer without retrievable text, so the OCR press release was read from a university-hosted PDF copy (privacy.unc.edu, an archived capture of the hhs.gov release) cited above; the hhs.gov resolution-agreement index page was also opened. Scale reporting moved between up-to-80 million (initial) and approximately 78.8 million (settled figure); the disclosure criticism rests on the Senate HELP letter and the multistate injunction term. Security-policy note: no consent-gated actions were needed; no leak sites or stolen data were consulted. Link check: help.senate.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: ohioattorneygeneral.gov was unreachable at check time (timeout); the page was opened and read during research. Link check: nytimes.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: hhs.gov blocks automated access (HTTP 403); the page was opened and read during research.