Germany's largest bank is under investigation by its home-state data protection regulator after about 15 million internal documents were leaked to an international media group. The documents include more than nine million emails. On Wednesday, 18 November, Hesse's data protection commissioner, Alexander Roßnagel, said he had opened proceedings. He is looking at whether Deutsche Bank had adequate safeguards in place, whether it reported the breach on time, and whether it told affected people without undue delay. Most reporting gives the size of the leak as 15 million documents (Reuters, Handelsblatt). Euronews and tagesschau describe it as "over" or "more than" 15 million. The bank has not given its own figure. Deutsche Bank says it has found no sign that its current IT systems were compromised. It says it notified authorities, including the data protection regulator, as a precaution. The bank's shares fell by as much as about 6% when the first reports came out.
What Happened
On Tuesday, 17 November, more than 50 media outlets began publishing stories based on the leaked files. The project is known as "Inside Deutsche Bank". AFP reports that more than 200 journalists worked on it. Outlets taking part include the Financial Times, Der Spiegel, Le Monde, The New York Times, ZDF, Der Standard, Follow the Money and South Africa's Financial Mail. In its statement, Deutsche Bank refers to the consortium as "Project Barracuda" and "Barracuda Media".
AFP and tagesschau report that the material came from whistleblowers. AFP says there were two. The files are said to have reached the wider group of outlets through journalists in South Africa and India.
A day later, Hesse's data protection commissioner opened an investigation. Handelsblatt reported it first, and Reuters confirmed it. Roßnagel said he is examining whether the bank "had taken suitable technical and organizational measures to ensure a level of protection appropriate to the risk". He is also checking whether the bank notified his office in time and whether it informed affected individuals "without undue delay". He has asked Deutsche Bank for more information and documents. He would not comment on possible sanctions. Under the GDPR, a breach that poses a risk to people's rights generally has to be reported within 72 hours of the company becoming aware of it.
Deutsche Bank told Reuters it had "proactively informed the appropriate authorities". In its own statement, the bank says it has contacted clients and staff it knows "may be materially affected". Neither the bank nor the regulator has said when Deutsche Bank first learned of the leak or when it filed its notification. That timeline is the main open question in the regulator's investigation.
The reports also hit the bank's share price. AFP reported that the stock fell nearly 6% shortly after the Frankfurt open on Tuesday. The Hindustan Times, citing Forbes, says it closed down 3.57% at €31.76 after a drop of more than 6% during the day.
What Was Taken
According to tagesschau and Handelsblatt, the files include more than nine million emails along with internal reports, presentations and calendar entries. AFP says they cover about 20 years of the bank's business. Deutsche Bank's statement says the documents "date back several years" and in some cases relate to matters up to two decades old.
The data is sensitive in two ways:
- Personal and client data. The bank says the material contains "confidential information about clients, employees and other third parties". Its clients have included Russian oligarchs, US President Donald Trump and Jeffrey Epstein. This personal data is what makes the leak a GDPR matter, whatever the public interest in the reporting.
- Internal compliance records. According to Der Spiegel and ZDF, as cited by tagesschau, the files show internal warnings about money laundering, sanctions and know-your-customer checks being repeatedly overridden. tagesschau reports that in late 2020 the bank planned to raise revenue from wealthy Russian clients from €28 million to €50 million by 2023. As part of that plan it reportedly compiled a list of the 200 richest Russians. The Financial Times reports that Epstein's relationship with the bank continued despite internal warnings. Financial Mail says his last two accounts were closed three days after his arrest in July 2019.
The files also point to an older mistake in how the bank handled data. The Financial Times reports that Deutsche Bank once accidentally sent a Trump tax document to another client's accountant.
The bank says that, based on testing carried out with an outside security firm, there is no sign that account information, login credentials or payment data were accessed. CEO Christian Sewing told Handelsblatt the same thing.
Why It Matters
This is not a ransomware attack or an outside intrusion. Based on what has been reported, it is a very large insider disclosure. For defenders, that changes the lessons:
- "Our systems weren't compromised" doesn't settle the matter. Deutsche Bank is right to separate its current environment from the leaked archive. Regulators still treat the loss of personal data as a breach, whoever took it out and whatever the reason. Roßnagel's investigation is about safeguards and how quickly the bank notified, not about who did it.
- Old data is still a liability. Emails up to 20 years old, still accessible and in bulk, made this leak possible. Every year of retained mail that nobody needs adds to what can be lost.
- Insider exfiltration at this scale should have been spotted. Nine million emails is a very large amount of data to move. How it left the bank without being detected, or whether it was detected and nothing was done, is likely to be central to the regulator's assessment of the bank's safeguards.
- The financial cost goes beyond fines. Shares fell on the day the reports came out, the CEO is facing personal questions in the press, and a GDPR investigation is now under way. Possible GDPR fines and further action by financial regulators could add to that.
The Attack Technique
The method has not been disclosed. The available facts are as follows:
- Media reports say the data came from whistleblowers. The bank describes it as "allegedly disclosed by whistleblowers" and says it cannot say more because of ongoing investigations and the legal protections whistleblowers have.
- Deutsche Bank says that after "extensive testing conducted together with a security firm", there is no sign its current IT environment is compromised. Sewing told Handelsblatt that "our systems today are not compromised".
- No one has said whether the whistleblowers were current or former employees, contractors or third parties. No one has said whether the data was taken in one go or over a long period, or which systems it came from, such as mail archives, document management or backups.
Nothing published so far suggests malware, stolen credentials or an outside threat actor. Until the bank or the regulator says more, the most reasonable reading is that people with legitimate access took the data out in bulk.
What Organizations Should Do
- Monitor bulk access to mail and documents. Alert on mailbox exports, large eDiscovery or journal queries, bulk downloads from document stores and unusual data volumes leaving through cloud sync, USB or personal email. Base the alerts on each user's normal behaviour, not fixed thresholds.
- Enforce retention and data minimisation. Delete email and files once their legal retention periods expire. Archives that must be kept should be locked down, with tight access, logging and approval for bulk retrieval.
- Treat insider disclosures as GDPR breaches in your incident plans. The 72-hour clock starts when you become aware of the breach, not when you find out who caused it. Prepare decisions on regulator notification and on notifying affected people for leaks that become public through the media.
- Make internal reporting channels credible. The EU Whistleblower Directive requires protected internal channels. If staff raise warnings and see them overridden again and again, they are more likely to go to journalists. Track whether escalated compliance warnings are acted on, and audit that.
- Prevent misdirected documents. The reported Trump tax document error is a reminder that sending sensitive documents to the wrong person is a breach in its own right. Use recipient verification, data loss prevention rules for regulated document types, and encryption with authenticated access for external delivery.
- Restrict access to the minimum needed. Review who can reach executive, compliance and client due-diligence material. Remove standing access to historical archives for anyone without a current business need.
Sources: Data watchdog probes massive Deutsche Bank leak of 15M files Euronews | Massive Deutsche Bank leak prompts investigation by data watchdog -... | Deutsche Bank shares drop after reports on mass data leak AFP.com | Deutsche Bank statement on recent media reports | Datenleck: Interne Dokumente belasten die Deutsche Bank tagesschau.de | Deutsche Bank: „Ich bin nicht fehlerfrei“ – Christian Sewing sprich... | Deutsche Bank shares fall as leaked files expose Epstein ties, Trum... | Data Protection Regulator Launches Investigation Into Deutsche Bank...