2016 · United States · J - Information and communication · Data theft via leaked cloud access credentials, followed by a concealed disclosure
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via leaked cloud access credentials, followed by a concealed disclosure
Strategy to Leadership
Evidence coverage: 4/6 stages, weight 34/60
Decisive stage: response (tie-break: post-breach stage) · Alternative: Expertise to Execution
(1) Strategic expectation: Uber held personal data of ~57 million riders and drivers while answering a pending FTC investigation into its data-security practices - its written-question duty covered any unauthorized access, state breach-notification law was triggered by the 607,000 driver's license numbers, and on 4 November 2016 the CSO testified under oath about the steps taken to keep customer data secure. (2) In practice: between 13 October and 15 November 2016 two intruders logged into Uber's private code repository with passwords exposed in earlier breaches (no MFA required, credential reuse unpolicy'd), found an AWS access key in plain text and copied 16 files of unencrypted PII on about 57 million people; Uber noticed none of it and learned of the breach only when an attacker emailed a ransom demand; the CSO then ran a cover-up - he told a subordinate they "can't let this get out", paid $100,000 in bitcoin in December 2016 through the bug-bounty administrator for NDAs falsely stating no data was taken, hid the incident from the General Counsel and the FTC, and lied about its scope to the incoming CEO; the new board-driven management found the truth and disclosed on 21 November 2017; Uber later admitted its officers concealed the breach from the FTC, the CSO was convicted of obstruction of FTC proceedings and misprision of a felony, and all 50 states plus DC settled for $148 million. (3) The classification rests on the response stage: the expectation was doctrinal (notification statutes, CID answer obligations, sworn FTC representations) and the chain broke at the decision level - senior officers knew the obligation and chose concealment, so this is a Strategy to Leadership gap, not an operation failing to execute a decision. The entry gap (leaked access key, no MFA/credential policy) and the egress gap (unencrypted crown-jewel stores) are known remedies never executed and form a clear secondary Expertise to Execution pattern that carries the largest share of the distribution, but under the tie-break the post-breach response stage prevails: it is furthest from the breach moment, rests on adjudicated primary sources, and explains why the impact became disproportionate (13 months without notice). The 2014 breach - same GitHub-key-into-AWS pattern, disclosed only months late, the very subject of the FTC investigation - shows the credential-handling weakness had recurred unremedied, which is described here rather than coded. (4) RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged outright from legal expectations - the breach was concealed from drivers, state regulators and the FTC for more than a year and surfaced only through an internal board review under new management (causal role: Constraining). RM42 (Strategy to Leadership lens): the extortion demand was met with no governed, authorised position - a $100,000 bitcoin payment disguised as a bug-bounty payout against NDAs, used to keep the incident from regulators, exactly the concealed-payment pattern the marker names (causal role: Constraining). RM44 (Strategy to Leadership lens): leadership presented a security posture it did not ensure existed - the CSO's sworn November 2016 FTC representations about protecting customer data stood against sensitive personal information stored in clear, readable text until at least November 2016 (causal role: Predisposing or obscuring). RM26 (Strategy to Leadership lens): data protection was never required commensurate with sensitivity - PII including driver's license numbers sat in unencrypted database backup and prune files, so the intrusion converted directly into the theft of ~57 million records (causal role: Amplifying).
RM39 — Breach notification / disclosure failureRM42 — Extortion-response governance gapRM44 — Public security-claim discrepancyRM26 — Data-protection / cryptographic weaknessinformationisbeautiful row: the dataset's source_url (Bloomberg, 21-11-2017) is paywalled - it opened to the headline only, so the analysis rests instead on the FTC revised complaint (read as a Wayback snapshot of the original ftc.gov PDF; the current ftc.gov path returns 404), DOJ releases, the multistate settlement, and Uber's own statement. The row's description matches the incident and is confirmed; one nuance: the CSO (Joseph Sullivan) did not merely resign - he was fired by the new CEO in November 2017 and convicted in October 2022 of obstruction of FTC proceedings and misprision of a felony (conviction affirmed by the Ninth Circuit in 2025), and the $100,000 was paid through the bug-bounty administrator in exchange for NDAs. Related rows are separate Uber incidents: row 748 is the September 2022 network intrusion (per its case file); no case files for rows 827 and 1079 exist in the run folder, so nothing is stated about them beyond the FTC complaint's own record of the 2014 breach (50,000 drivers, access key posted to GitHub) as the antecedent under FTC investigation. Year 2016 = incident year (downloads 13 Oct - 15 Nov 2016); disclosure was November 2017. Sector: Uber's core activity is ride-hailing (arguably H), but per the method-spec rule that IT/software/technology companies classify under J, the code is J. The FTC action is a settlement allegation for the monitoring finding (hence primary-open at the detection stage); the concealment facts are admitted/criminal-record level. Link check: uber.com blocks automated access (HTTP 406); the page was opened and read during research.