← Breach analysis by the Dual Vulnerabilities framework

NRA Bulgaria mass data leak (Unattributed, 2019)

2019 · Bulgaria · O - Public administration and defence · Mass data theft (databases exfiltrated and emailed to media)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Mass data theft (databases exfiltrated and emailed to media)

Dual vulnerability type

Strategy to Execution

Evidence coverage: 4/6 stages, weight 28/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) The strategic expectation at the Bulgarian National Revenue Agency was explicit and doctrinal: as the state data controller of the consolidated taxpayer register it owed Art. 32 GDPR appropriate technical and organisational measures (ongoing confidentiality, monitoring, protection of its public e-services) before any attacker appeared, and its leadership had adopted a strategy of expanding electronic services. (2) In practice the doctrine never reached execution: the CPDP's inspection established that the Agency had not implemented the appropriate measures in its internal procedures, activities and processing; the intrusion - reported as most likely through the VAT-refund e-service, an entry vector that is reported but not conclusively established and is not load-bearing for this classification - went unnoticed for about 20 days (the NRA's own statement of 16 July 2019: accessed approximately 20 days ago), and around 11 GB in 57 databases covering 6,074,140 people, including deceased persons and data received from other agencies, was exfiltrated without any detection or interruption; the theft surfaced only because the attacker emailed the data to journalists on 15 July 2019. The regulator fined the Agency BGN 5,100,000 for violating Art. 32(1)(b) and ordered within six months the very artefacts that should have existed before: protection of the e-services applications, system risk analyses and impact assessments. (3) That is a Strategy to Execution gap, not merely weak security: the expectation was doctrinal (a statutory duty the agency itself invoked when it notified and cooperated), and the chain broke in execution, because the measures were never realised in the applications, procedures and monitoring - the decisive stage is the entry condition (clearest evidence, documented by the regulator), with the month-long detection failure as the same mechanism's twin; no source shows leadership deferring or overruled a documented requirement (which would move it within the doctrinal column to leadership) or experts warning and being ignored (Expertise to Leadership); the response-stage narrative gap (public account lagging the facts, disclosure forced by the attacker) is real but post-breach and yields to the documented pre-breach condition. RM02 (Strategy to Execution lens): security requirements were weakened and omitted where they conflicted with the delivery goal of ever more electronic services - the executive director's own admission that the agency's drive was to offer an increasing number of electronic services but it underestimated the balance between access and security shows the systematic subordination of the requirement to the transformation objective (causal role: Predisposing). RM03 (Strategy to Execution lens): the Art. 32 obligation existed and was acknowledged before the incident, but it was never translated into the controls, evidence and processes required to comply - the CPDP's corrective orders list exactly the compliance artefacts (application protection, risk analyses, impact assessments) missing beforehand (causal role: Predisposing). RM16 (Strategy to Execution lens): classification, minimisation and privacy obligations were not operationalised in systems, so the breached service could reach the full register - income, tax, insurance and cross-agency records of 6,074,140 people, files dating back to 2007 - vastly more than a VAT-refund application needed (causal role: Amplifying). RM34 (Strategy to Execution lens): the monitoring and alert-handling that the doctrine assumed was not implemented or operated as intended - a 20-day dwell time ended only by the attacker's own media contact, the textbook time-to-detect failure (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Case-file source_url not usable: the zdnet.com article and the dnevnik.bg article both failed to open (HTTP error) during research and were replaced by the sources actually read and cited here. The victim's own disclosure page (nra.bg) and the CPDP press release were read; the CPDP page was opened via its web.archive.org snapshot shown, because cpdp.bg itself fails TLS handshake from this host. Attribution stays 'Not attributed' as in EuRepoC: an anonymous attacker emailed the data; Bulgarian prosecutors pressed cyber-terrorism charges against three people (reported July 2019); follow-up reporting (2023 plea deal) was seen in search results only and is not used as evidence. The attacker's claims of an earlier 2012 theft and of leaking for 11 years are unverified attacker claims and were not used. The CPDP fine of BGN 5,100,000 was announced with the agency saying it would appeal (Sofia Globe, 29 Aug 2019); the final court outcome of the fine was not verified in this task. EuRepoC dates the incident 01.01.2019-15.07.2019; reporting places the intrusion in June-July 2019; Year set to 2019. Weighted intensity of 1 in EuRepoC understates a leak covering most of an EU member state's adult population. Link check: nra.bg was unreachable at check time (timeout); the page was opened and read during research.