← Breach analysis by the Dual Vulnerabilities framework

Deutsche Leasing Data theft (Unattributed, 2023)

2023 · Germany · K - Financial and insurance activities · Cyber attack with data theft (IT shut down as countermeasure)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyber attack with data theft (IT shut down as countermeasure)

Dual vulnerability type

Strategy to Execution

Evidence coverage: 1/6 stages, weight 10/60

Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Deutsche Leasing AG, the leasing arm of Germany's Savings Banks Finance Group, is a supervised finance company holding personal data of a wide circle of counterparties; its doctrinal expectation was explicit: GDPR controller obligations that it itself operationalised through Art. 34 (3) lit. c GDPR notifications, plus a documented contingency plan. (2) The attack of 3 June 2023 was detected the same day by the company's own security systems and the contingency plan was followed (immediate shutdown, authorities and external forensics involved), so intrusion detection, containment conduct, recovery and disclosure were aligned; yet the completed forensic analysis found that attackers accessed individual servers and documents despite the immediate countermeasures, and no internal control detected or stopped the data outflow: the theft surfaced only about three months later, when a darknet-monitoring service the company had itself commissioned found its documents published, with the company conceding it could not exclude further outflow. (3) This is a knowing-doing gap of the doctrinal-to-execution kind, and it sits in the egress stage, the only stage with a documented victim-side gap and the decisive one: the obligation to protect this data was documented at strategic level, but it never became an effective operational barrier, so exfiltration went undetected by the victim's own security operations while leadership behaviour (fast shutdown, regulator coordination, prompt Art. 34 notification) was sound - which rules out Strategy to Leadership, while no source documents an expert-identified remedy that was ignored, which keeps it out of the Expertise column. The entry vector is undisclosed and not load-bearing. RM35 (Strategy to Execution lens): the victim's doctrinal duty to protect the personal data it held was never translated into an effective egress barrier - data left the network unnoticed and only a commissioned outside darknet screen, not the victim's own monitoring, revealed the theft about three months on (causal role: Amplifying). RM16 (Strategy to Execution lens): the leaked material included identity-document copies, tax identification numbers and account/bank data of legacy and peripheral populations (former employees, former committee members, applicants, guarantors), showing that classification, retention and minimisation requirements were not implemented in systems and processes, so the undetected outflow exposed more sensitive and older data than necessary (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Victim's own incident pages: the original German page (www.deutsche-leasing.com/de/unternehmen/cyberattacke-aktuelle-information) and the Bulgaria Art. 34 notice now return 404 after a website relaunch; the 1 September 2023 press release and the Deutsche Leasing USA/Canada Art. 34 notice cited here were opened live during research. Attribution: the row and the victim speak of unknown actors; ransomware trackers index a Black Basta leak-site entry of 17 August 2023 claiming the attack, unconfirmed by the victim, authorities or the German reporting - the leak site and its indexes were not opened and the claim is not load-bearing. Data-quality: the dataset codes the theft as non-sensitive information (1 point in intensity) while the victim's own Art. 34 notice lists identity-card/passport copies, tax IDs and account/bank data among exposed data. The dataset's functional_impact 'Days (< 7 days)' understates the restart timeline in September 2023 reporting, when the forensics had only then been completed and interfaces were being brought back step by step; recovery is not load-bearing. No source discloses the entry vector or any dwell time before the same-day detection on 3 June 2023.