← Breach analysis by the Dual Vulnerabilities framework

Sony Pictures destructive attack (North Korea, 2014)

2014 · United States · J - Information and communication · Destructive cyberattack with mass data theft and extortion

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Destructive cyberattack with mass data theft and extortion

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 5/6 stages, weight 38/60

Decisive stage: response (tie-break: post-breach stage) · Alternative: Expertise to Execution

Why this classification

(1) The strategic expectation at Sony Pictures was that cyber risk sat inside an accountable management posture: SPE employed an information-security function whose own executive director had publicly framed breach risk as something that may be accepted as a valid business decision, i.e. leadership owned the risk trade-off at strategic level. (2) In practice, leadership ran that trade-off down for years - an 11-person security team for 7,000 employees with few resources, internal reports of security violations repeatedly ignored (detection stage), plaintext password handling and unencrypted salary, revenue and medical records (entry and egress stages), and a network so flat that one wiper wave put the entire company network offline as the only containment (containment stage, not separately sourced) - and when the breach landed, the CEO's chosen communication was Mandiant's memo that the attack was unprecedented and that neither SPE nor other companies could have been fully prepared, while the studio's first public line on 24 November was that it was investigating an IT matter and disclosure happened only through the attackers' leak campaign. (3) This is not merely weak security: the gap sits within the doctrinal column. Leadership knew and owned the risk posture (doctrinal origin - the documented risk-acceptance stance, the tolerated understaffing, the ignored internal warnings) and the chain then broke at the decision level, where leadership communicated the incident inaccurately after the fact - a public narrative of unpreventability contradicted by the organisation's own documented pre-breach condition (leadership break). The classification rests on the response/disclosure stage; the entry vector (spear-phishing and stolen administrator credentials, per reporting citing US officials and the investigation) is load-bearing for distribution but never officially disclosed in primary terms and is not what makes the DV-Type. The entry, containment and egress gaps individually read as Expertise to Execution (known remedies not executed), but under the tie-break they describe the breach moment and lose to the post-breach response stage. (4) RM06 (Strategy to Leadership lens): leadership's risk appetite - the 2007 risk-acceptance statement and years of an 11-person team for 7,000 staff - did not reflect the materiality of the threat SPE openly faced, tolerating persistent deviation from any real security posture (causal role: Predisposing). RM07 (Strategy to Leadership lens): employees who repeatedly reported security violations to the information security team were ignored, so material risk signals never reached the decision-makers who set priorities (causal role: Obscuring). RM22 (Strategy to Leadership lens): leadership never required an authentication and credential model consistent with the risk - passwords pasted into plaintext email, easy-to-guess passwords, no two-factor protection even on code-signing certificates - and the attack succeeded by logging in with stolen administrator credentials (causal role: Enabling). RM39 (Strategy to Leadership lens): leadership disclosure diverged from what it knew - the attack was minimised to an IT matter on 24 November, acknowledged only as attacker leaks mounted, and the unrevoked leaked certificate stayed usable to sign malware until 7 December (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

The row's Time source URLs now serve sponsored placeholder text instead of the 2014 articles, so the cited links are the Wayback snapshots opened during this task. The FBI press release (primary) covers impact and attribution; the initial infection route (spear-phishing, stolen administrator credentials) comes from press reporting citing US officials and the investigation, not from a primary source, and the FBI itself gives no entry vector. The containment gap is recorded at inference level: no opened source explicitly states the network lacked segmentation; it is read from the documented fact that one malware wave reached half the fleet and a full network shutdown was the only containment. Recovery was severe but no backup-preparedness gap is documented by the sources opened, so it is recorded as no gap. Related rows 1105 and 1197 have no case files in this run's folder and no existing results; row 1197's title points to the 2011 LulzSec incident at Sony, but no opened source establishes a comparable earlier weakness, so RM21 was not coded. The description matches the stated victim (no data-quality mismatch). The FBI release credits Sony with reporting within hours of discovering the intrusion, so no notification-to-government failure is coded. Link check: forbes.com blocks automated access (HTTP 403); the page was opened and read during research.