← Breach analysis by the Dual Vulnerabilities framework

Starbucks employee-data laptop theft (Unattributed thief, 2008)

2008 · United States · I - Accommodation and food service activities · Data theft via stolen unencrypted laptop

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via stolen unencrypted laptop

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 18/60

Decisive stage: egress (tie-break: largest share) · Alternative: Strategy to Execution

Why this classification

(1) Strategic expectation at the victim: holding social security numbers for a workforce of about 97,000 partners carried the standing expectation that this crown-jewel data would be protected differently from ordinary data on any device it touched, and after a 2006 incident (four computers holding data on over 60,000 employees and contractors disappeared) Starbucks itself announced a policy forbidding critical data such as SSNs on mobile equipment. (2) What happened: a laptop was stolen on 29 October 2008 carrying the unencrypted names, addresses and SSNs of approximately 97,000 current and former employees; Starbucks's own notification letter of 19 November 2008 states the company was only 'currently implementing encryption solutions where appropriate', i.e. the known remedy of encryption was not yet realised when the device was taken; no misuse was ever established, and the Ninth Circuit later found a 'credible threat of real and immediate harm' from the unencrypted data while the state-law claims were dismissed for want of cognizable damage. (3) The classification rests on the egress / data-governance stage: the remedy (encryption at rest of portable assets holding SSNs) sat with technical specialists as a known, available control and Starbucks's letter confirms operations had not deployed it before the incident, so origin is material and the break is execution - a gap within the material column (Expertise to Execution). The entry condition is a secondary Strategy to Execution pattern: the 2006 policy existed doctrinally but a laptop still held 97,000 SSNs, a policy-practice gap; the two conflicting pre-breach conditions carry no documented causal link, so the tie-break went to the largest share, which belongs to the primary-documented egress gap. The entry vector itself (an unattributed physical theft) is not load-bearing. Response and detection were prompt and are not coded as gaps. RM11 (Expertise to Execution lens): the specific policy - the mobile-data rule announced after the 2006 incident - existed, but workforce data-handling practice did not follow it, the 2008 laptop carrying SSNs of ~97,000 people being the documented non-compliance (causal role: Perpetuating). RM21 (Expertise to Execution lens): an earlier comparable incident in 2006 with the same loss mechanism produced an announced remedy, yet by 2008 the known technical safeguards (keeping critical data off mobile equipment, encryption) were still not implemented or validated, so the same weakness recurred at larger scale (causal role: Perpetuating or learning-blocking). RM25 (Expertise to Execution lens): the company's own equipment and storage media left the physical perimeter unprotected and unencrypted - the exclusion for encrypted devices does not apply because exposure of the unencrypted data is exactly what happened (causal role: Enabling). RM26 (Expertise to Execution lens): data at rest was held with no encryption at all, so one stolen device exposed the full 97,000-record data set; the letter's admission that encryption was only then being implemented shows the cryptographic control was not realised in operations (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

informationisbeautiful row: the case file carries only one sentence, so all lifecycle evidence comes from own research. The dataset source_url (infowatch.com leaks listing) is a directory page, not an article, and was not cited. The row's description is loose but matches Krottner v. Starbucks: the Ninth Circuit (14 December 2010) held employees had standing (a credible threat of identity theft from the unencrypted data) but affirmed dismissal of the negligence and implied-contract claims because no cognizable harm under Washington law was pleaded, which matches the row's account of employees winning before losing in federal court. Year 2008 = date of the theft (29 October 2008); disclosure letters 19 November 2008. The 2006-incident detail (four computers, 60,000+ records, announced mobile-data policy) rests on SC Media citing KOMO News and on CSO Online (both secondary); the unencrypted state of the data and the notification terms rest on primary sources (Ninth Circuit opinion and the notification letter filed in the docket). Actor is an unattributed thief; attribution is not a DV claim. Recovery and containment were not in play (physical device theft, no services affected). Link check: law.justia.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: courtlistener.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: nothing encountered that required consent.