2016 · Austria · O - Public administration and defence · DDoS attack on a government website causing short-term disruption
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS attack on a government website causing short-term disruption
No DV evidenced
Alternative: Expertise to Execution
(1) Strategic expectation at the victim: by 25 November 2016 the ministry's public web presence was a known, openly signalled target - since September 2016 a series of politically motivated flood attacks had hit the Vienna airport, the National Bank, the defence ministry and other Austrian institutions, the national coordination structures warned of further waves (the official report records that the coordination structures predicted individual attacks two hours ahead), and the expectation was that a ministry under this pressure would detect floods on its public web front fast, keep internal systems separated from it and communicate accurately. (2) In practice: the attack targeted only the web server; the flood made the ministry notice it immediately, the ministry took the site offline itself, set defence measures jointly with the Federal Office for the Protection of the Constitution and the Defence Ministry, its internal systems remained unaffected, no data left, the page was reachable again from 23:00 the same evening (first domestically, then internationally), and the Foreign Minister's public statement the next day matched the documented facts; the official annual cyber security report reviews the whole attack wave this row belongs to and finds the victims evidently well prepared, only comparatively minor outages and no business- or security-critical system failure in a single case. (3) That is not merely an absence of bad news: each lifecycle stage that came into play shows controls executed as doctrine prescribes, and the one realised loss - a roughly 4.5-hour interruption of the attacked public page - was bounded by the victim's own protective shutdown to the attacker's own target surface; nothing in the sources places an expectation or knowledge that went unacted upon in either column, so the regulator-finding rule applies and the case is a confirmed negative: No DV evidenced. The entry vector (a volumetric flood against a public web server) is an attacker-side technique and is not treated as a victim-side gap. The two coded markers describe the conditions the incident actually showed, without a DV claim: the availability of the public web service could not be sustained under the flood, which is why the response was a protective shutdown, and the ministry's whole web presence hung on that single serving path, so the only response option was a full-site shutdown with a stepwise restoration (first Austria-only, then international).
RM32 — Capacity / availability-protection gapRM04 — Control dependency concentrationEuRepoC row; the case file's description matches its stated victim (no data-quality mismatch). Victim named from receiver_category plus the sources: the BMEIA website, attacked Friday 25.11.2016. Actor: the case file records initiator Unknown and an anonymous government-circle attribution; the official Bericht Cyber Sicherheit 2017 attributes the whole attack series to Aslan Neferler Tim on the then state of knowledge and finds no evidence of active Turkish state participation, so the actor is recorded as ANT with that caveat. A Facebook responsibility claim by ANT for this specific attack is reported by RT (opened) but was not corroborated in the Austrian sources opened; RT also reports the ministry initially attributed the outage to technical problems at the website provider before admitting a hack on the Saturday - uncorroborated in the sources opened, so no disclosure marker is coded on it and the case file's disclosure-by-attacker entry is read against ANT's public claim, with the ministry's own public account following via APA on 26.11.2016. heise and welt URLs cited are the final article addresses opened (they redirect from the case file's source_url values). The BMI magazine article (Oeffentliche Sicherheit 5-6/17, summarising the BVT SKI report) independently records that all victims of the 2016 attack wave were apparently well prepared and no security-critical system failed. Later, separate incidents at the same victim (Bundesheer website 28.11.2016, BMEIA website again in July 2017) were identified in the search record but are not part of this row and were not used for the classification. Link check: the direct bmi.gv.at URL of the Bericht Cyber Sicherheit 2017 now answers 404 to automated fetches, so the report is cited through the web.archive.org snapshot (2026-05-08) that was opened during this task and whose section 1.1.2 was read from the archived PDF; the BMI magazine article link still resolves. Unattended run: nothing in this task required an action the security policy gates behind consent.