← Breach analysis by the Dual Vulnerabilities framework

AshleyMadison.com data theft and leak (The Impact Team, 2015)

2015 · Canada · J - Information and communication · Data theft and extortion with public leak

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft and extortion with public leak

Dual vulnerability type

Strategy to Leadership

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

Decisive stage: entry (tie-break: cause) · Alternative: Expertise to Execution

Why this classification

(1) AshleyMadison.com's owner Avid Life Media sold discretion as its product: a senior executive told the Commissioners that 'the protection of our customer's confidence is at the core of our brand and our business', the site displayed a security trust-mark, and PIPEDA Principles 4.1.4/4.7 obliged a framework of policies and safeguards commensurate with the sensitivity of the data - the expectation was doctrinal, originating in ALM's own strategic promises and legal commitments. (2) In practice that framework did not exist at the July 2015 breach: no documented information security policies (para 65), no risk management framework (para 69), external cybersecurity expertise considered and declined (para 71), MFA for administrative remote access a decision not taken (para 73), security training reached only about 25% of staff (para 74); an attacker with one compromised single-factor VPN credential held access for months, escalated to administrator and erased logs (paras 19, 60-61), while retained data of users who had paid for 'Full Delete' was among what was published (FTC; PIPEDA 4.5.2 contravention). (3) This is a Strategy to Leadership gap rather than merely weak security: the knowing-doing break sits inside the doctrinal column - leadership knew what the brand and the law required, weighed external expertise and MFA as options, and decided against them, so the security framework the company's own strategy demanded was never established; the joint report makes the causal ordering explicit - the lack of an adequate framework 'failed to prevent the multiple security weaknesses described above' (para 79). The classification rests on the entry stage (the pre-breach condition that made administrative remote access reachable in that state); it won the tie-break over the E2E reading of the containment and detection gaps because the source documents the framework gap as the cause of those technical gaps. The entry vector itself (compromised valid VPN credentials) is documented but is not the basis of the DV-Type. (4) RM11 (Strategy to Leadership lens): leadership never established a policy commensurate with the organisation's stated strategy - the specific missing artefacts named by the investigation are documented information security policies for managing network permissions and a documented risk management framework, found to contravene APP 1.2 and PIPEDA Principles 4.1.4 and 4.7 (causal role: Perpetuating). RM22 (Strategy to Leadership lens): leadership did not require an authentication model consistent with the risk it marketed: VPN remote administrative access relied on a single factor (a shared secret, also stored on the company's Google Drive) and the Commissioners called 'ALM's decision not to implement multi-factor authentication for administrative remote access' a significant concern (causal role: Enabling). RM44 (Strategy to Leadership lens): leadership presented a security posture it did not ensure existed - the 'trusted security award' trust-mark was ALM's own fabrication, contradicted by the framework deficiencies and misrepresentations the regulators documented (causal role: Predisposing). RM16 (Strategy to Leadership lens): leadership commitments on data responsibility were not reflected in its decisions: the paid 'Full Delete' promise stood against indefinite retention of deactivated accounts, a 12-month retention after deletion and photos of deleted accounts never destroyed, with no maximum retention periods ever set (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Victim operates as AshleyMadison.com; parent company Avid Life Media Inc. (Toronto, rebranded ruby Corp in July 2016) - regulator findings cited are addressed to ALM. The row description matches the incident: Krebs confirms user data plus internal financial records were stolen and threatened with release. Year recorded as 2015 (breach discovered 12 July 2015, leaks 18/20 August 2015); the FTC alleges intrusions as early as November 2014 and the OPC that access lasted 'at least several months', so the intrusion predates the recorded year. incident_id not carried by the case file; no related_rows. Outcomes: OPC compliance agreement, OAIC enforceable undertaking, FTC/state settlement of USD 1.6m (USD 8.75m judgment partly suspended). Link check: both FTC pages cited (press release of 14-12-16 and business-guidance blog) now return 404 live; the content was read via web.archive.org and the opened snapshot URLs are cited instead. Unverified attacker claims were not used; attacker-leaked internal documents were referenced only via Krebs's reporting and are not load-bearing for the classification.