2012 · Belgium · H - Transport and storage · Accidental publication of customer data on a public web server
Analysed 2026-11-07 by Hermes
Open this case in the tool →Accidental publication of customer data on a public web server
Strategy to Execution
Evidence coverage: 4/6 stages, weight 19/60
Decisive stage: entry (clearest evidence) · Alternative: Strategy to Leadership
(1) Strategic/doctrinal expectation: NMBS/SNCB, the Belgian national railway operator, was a public body and data controller under the Belgian privacy duty, with an explicit obligation to keep customer personal data off public systems - the Privacy Commission stated that NMBS is responsible for breach of privacy of the affected customers, and NMBS's own spokesman acknowledged the customer list should not have been made public. (2) In practice: shortly before Christmas 2012 a bulk export of about 1.46 million customer records (names, genders, dates of birth, email addresses, and in some cases home addresses and phone numbers) was published on the public b-europe.com web estate with no authentication mechanism, was indexed by search engines, and was found on 22 December 2012 by an external forum user via a trivial query (reported as 'inurl:b-europe.com filetype:txt'); the file was quickly downloaded by many and later copied onto another site. NMBS attributed the cause to a data worker 'clicking on the wrong button'. There is no attacker: the 'entry' is the organisation's own exposure of the data. (3) The classification rests on this exposure (entry) stage: the doctrinal privacy obligation was acknowledged yet did not translate into operational reality - no publication check or four-eyes control stopped a single wrong click from exposing 1.46 million records to the open web, and no source shows any decision to publish customer data, so the chain broke in execution rather than at the leadership level: Strategy to Execution. The response stage is a documented secondary Strategy to Leadership pattern (the spokesman initially claimed the accessible file was private because its URL was not revealed and that the discoverer used a technique, contradicting the trivial search path; no victim notification; the Commission filed a report with the federal prosecutor), but it worsened rather than caused the impact, so it is contributing, not decisive. The detection gap (an outside forum user, not NMBS monitoring, found the leak) rests on inference and is likewise contributing. (4) RM27 (Strategy to Execution lens): exposure rules for deployed systems were not applied - 1.46 million customer records sat in an unauthenticated plaintext file on the public web estate, reachable by a simple search-engine query (causal role: Enabling). RM46 (Strategy to Execution lens): safeguards for handling and publishing data - publication checks, four-eyes review, DLP - were not implemented, so one worker's wrong-button action exposed the whole customer export without any control catching it (causal role: Enabling). RM39 (Strategy to Execution lens): notification duties were not operationalised as a workflow - affected individuals were left to write to SNCB with a copy of their identity card, no proactive notification followed, and the public account initially misstated how the data had been reached (causal role: Constraining).
RM27 — Configuration hardening / external exposureRM46 — Accidental disclosure / data-handling errorRM39 — Breach notification / disclosure failureCase-file description matches the victim (NMBS = the Dutch name of SNCB/NMBS; the leak occurred on its SNCB Europe / b-europe.com web estate), so no mismatch. The case-file source_url carries a trailing ' /' formatting artifact in the dataset; the article itself opens fine at the quoted URL. Scale figures differ across sources: the Privacy Commission's early estimate was about 700,000 affected people (Flanders Today), while NURPA's count of the file was 1,460,735 records and Politico reported 1.5 million; the case file's 'thousands' of searchable records understates it. Exposure duration is unconfirmed: Politico says the folder was uploaded just before Christmas, while other coverage says weeks; this does not affect the classification. The Commission's report to the federal prosecutor is reported, but no follow-up prosecution or sanction record was found in the searched record (searched, not found). 2012 Belgium imposed no breach-notification duty; RM39 is coded for the inaccurate public account and the absence of any workable victim-information route, not for a legally required notification. No threat actor: no attribution or attacker-side claims.