2011 · Japan · J - Information and communication · Network intrusion and mass theft of customer account data
Analysed 2026-11-06 by Hermes
Open this case in the tool →Network intrusion and mass theft of customer account data
Strategy to Execution
Evidence coverage: 3/6 stages, weight 19/60
Decisive stage: egress (tie-break: largest share) · Alternative: Expertise to Execution
(1) Strategic expectation: Sony operated the PlayStation Network / Qriocity account platform as data controller for some 77 million registered users and was obliged to hold no more personal data than the service needed and to protect it with appropriate, up-to-date technical measures; its own April 26, 2011 customer notice promised to rebuild the system to give customers greater protection of their personal information. (2) In practice, an intruder entered between April 17 and 19, 2011 and exfiltrated the account trove largely undetected; the UK regulator later found the attack could have been prevented had the software been up to date, that Sony stored excessive amounts of customers' personal data (itself a DPA breach), and that the Network Platform service provider had not kept up with technical developments such as cryptographic controls for passwords, concluding the security measures in place were simply not good enough. (3) The classification rests on the egress/data-governance stage: the unmet expectation is doctrinal in origin (data minimisation, retention and protection obligations that bound Sony precisely because of the platform's scale), and per the regulator's findings the chain broke in execution - the obligations were never realised in the platform's systems and stored-data reality, which made the exfiltration as large and as sensitive as it was; no source shows leadership deferring or discounting these obligations, so it is not Strategy to Leadership. The entry condition (out-of-date software with a known remedy) is a documented, load-bearing pre-breach gap pointing to Expertise to Execution, but the two pre-breach conditions have no source-documented causal link, so the largest-share rule decides in favour of the data-governance finding. Detection (own team within about two days) and recovery (deliberate rebuild, full restoration June 9, 2011) show no documented gap; the week between detecting credible intrusion indications (April 19-20) and notifying customers (April 26) contributes but its internal cause is undocumented. RM18 (Strategy to Execution lens): vulnerability-management requirements for the platform were not translated into timely updating and patching - the ICO found the attack could have been prevented had the software been up to date, and the intrusion exploited a vulnerability in outdated software (causal role: Enabling). RM16 (Strategy to Execution lens): minimisation and retention requirements were not implemented in the platform - the ICO found Sony stored excessive amounts of customers' personal data, so the data exposed was more than the service's purposes required (causal role: Amplifying). RM26 (Strategy to Execution lens): password and data-protection requirements were not implemented in storage - cryptographic controls had not kept up with technical developments, so the stolen account credentials and payment-card trove left the platform in weaker protection than the obligation required (causal role: Amplifying).
RM18 — Vulnerability / patch latencyRM16 — Data governance / minimisation gapRM26 — Data-protection / cryptographic weaknessinformationisbeautiful row: the description is the only input; all lifecycle evidence comes from own research. Data-quality remarks on the row's description: it states 76,000,000 accounts while contemporaneous reporting (Reuters, Guardian) and Sony give 77 million; it says the services were offline for 23 days while Sony's own June 9, 2011 press release shows the full April 20 - June 9 shutdown (gaming services returned in stages in late May); the 'third breach' count is the dataset's numbering and was not verifiable from the sources opened, so no recurring-weakness marker (RM21) is coded. The case file's source_url (blog.playstation.com/archive/2011-04-28/playstation-network-and-qriocity-outage-faq/) returns 404 and no openable archive snapshot was found, so the April 26 disclosure and outage timeline are cited to contemporaneous reporting (Reuters, Guardian, WIRED) instead. The ICO monetary penalty notice itself (14 January 2013, GBP 250,000 against Sony Computer Entertainment Europe) is available only as a scanned PDF with no text layer and image analysis was unavailable in this environment, so its findings are cited via the opened secondary reporting (BBC, Pinsent Masons/Out-Law), which quote the notice. Actor unattributed: the pre-breach DDoS campaign reported to be linked to 'Anonymous'/LulzSec is context only and was not load-bearing for the DV reading. Link check: reuters.com blocks automated access (HTTP 401); the page was opened and read during research. Link check: sony.com blocks automated access (HTTP 403); the page was opened and read during research. Security policy: only public pages were consulted; no leaked data or leak-site material was used; nothing in the sources required a consented action.