← Breach analysis by the Dual Vulnerabilities framework

SCMLC Unsecured Workers' Comp Data Exposure (No Actor, 2011)

2011 · United States · Q - Human health and social work activities · Unsecured data exposure on an unintentionally public web server

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Unsecured data exposure on an unintentionally public web server

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 16/60

Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) As a California firm handling workers'-compensation billing and medical-legal data for medical providers, SCMLC was expected to keep claimant records containing names, Social Security Numbers and physician notes access-controlled, unindexable and protected; its president invoked exactly this expectation in the company's own June 2011 press release, stating that internal security policies and procedures existed and that the company was doing everything required under the law with respect to notification. (2) In practice, electronic files on roughly 300,000 benefit applicants were published on a web server the owner believed only employees could use: without password protection, without instructions to keep search engines from indexing the pages, and unencrypted, so the records were findable and readable through Google; SCMLC never detected this itself - an Identity Finder researcher's automated Google-index search found the exposure (May 2011) and alerted the firm. (3) This is a knowing-doing gap inside the doctrinal column's counterpart - a Strategy to Execution gap: the expectation existed at policy level (the president's own statement that the firm's internal security policies and procedures were not followed concedes the artefacts applied to this data), but it never translated into operational reality on the machine where the crown-jewel data was held; the classification rests on the entry/exposure stage, the best-documented gap. The break is in execution rather than leadership because no source shows leadership deferring, under-resourcing or accepting the need - the need was stated and the controls simply were not realised; the president declined to explain how the files got online, so an alternative reading (policies that never covered this server) is noted as the open question. Detection (exposure found by an outside party, not by own monitoring) and egress (sensitive data neither encrypted nor access-restricted) are contributing stages; no attacker and no entry vector is involved, and recovery and response were handled promptly. (4) RM27 (Strategy to Execution lens): configuration baselines and exposure rules were not applied to the deployed system - the supposedly internal files ran on a public web server with no authentication and no search-engine exclusion, the exact form of exposure such rules exist to prevent (causal role: Enabling). RM15 (Strategy to Execution lens): the company's picture of its own exposure paths was wrong - the owner believed the site was employees-only while it was Google-visible, so asset-management and data-flow requirements were not reflected in what the organisation actually knew about its own systems (causal role: Enabling). RM26 (Strategy to Execution lens): data-protection requirements were not implemented in storage - names, Social Security Numbers, insurance forms and physician notes were held unencrypted and readable by anyone who reached them, which amplified the blast radius of the single exposure (causal role: Amplifying). RM46 (Strategy to Execution lens): no safeguards for handling and publishing data (access checks, four-eyes review, publication checks) were implemented, which is why an internal-intended repository could be published to the world without anyone noticing (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

informationisbeautiful row: description matches the victim and the case file's source_url; no incident_id, so it stays null; no related_rows for this victim. No attacker: the case is an accidental exposure found by an external researcher, so the entry stage is coded as an exposure gap, not an intrusion. The president's quote that internal security policies and procedures were not followed is SCMLC's own self-characterisation; he declined to give further detail (how the files were published, exposure duration), and the incident was still under investigation when the AP story ran in August 2011 - the origin reading rests on this primary self-report, which is why the entry stage is primary-open rather than primary. No regulator action (OCR/HIPAA enforcement), litigation or state sanction against SCMLC was found for this incident; the incident was reported not to appear on the federal tally of major health-information breaches at the time. Link check: workcompwire.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research.