2023 · Belgium · O - Public administration and defence · DDoS attack causing temporary unavailability of public websites
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS attack causing temporary unavailability of public websites
Expertise to Execution
Evidence coverage: 1/6 stages, weight 6/60
Decisive stage: recovery (clearest evidence) · Alternative: Strategy to Execution
(1) The expectation at these federal institutions was that their public websites stay reachable: DDoS mitigation (capacity scaling, filtering, anti-DDoS services) is a standard, available technical remedy, and Belgium's national cyber security centre actively monitors the pro-Russian flood campaigns and warns institutions of imminent attacks. (2) In practice, on 9 November 2023 flood traffic again made the Chamber of Representatives, Senate and Royal Family websites unreachable (Chamber requests timing out), barely a month after the same group had taken the same sites down in mid-October; the CCB confirmed the targeting, said it had warned the concerned services, and stated the hindrance remained limited, with the sites back within a day and no data affected. (3) That is a knowing-doing gap inside the material column: the remedy is known expertise, the traffic was even signalled in advance, yet operations did not keep the services online - the break is in execution, not in leadership or doctrine, since no source documents a deferred policy, an unfunded programme or an ignored expert warning (the origin and break of the availability gap are inferred from the documented facts; no source states them). The entry vector (DDoS flood) is known but not load-bearing: it describes the attacker's move, not a victim-side access failure; the classification rests on the recovery/availability stage, the only stage with a documented victim-side gap. (4) RM32 (Expertise to Execution lens): the institutions could not keep their public services available under the flood despite known mitigation options - the sites were offline for hours, so capacity and denial-of-service protection did not hold in operations (causal role: Enabling). RM21 (Expertise to Execution lens): an earlier comparable weakness is documented - the identical sites were DDoSed in mid-October 2023 - and the recurrence on 9 November shows the post-October adjustments were not implemented or validated in a way that withstood a renewed attack (causal role: Perpetuating).
RM32 — Capacity / availability-protection gapRM21 — Recurring weakness / learning failureEuRepoC row; description matches the stated victims (no data-quality mismatch). Attribution rests on the group's self-claims on X/Telegram as reported by the press - the attacker's Telegram channel (t.me/noname05716/5234, in source_url) was not opened per policy on attacker channels. The incident was thinly reported: the live HLN article is behind a privacy gate, so the archived snapshot cited was opened and read instead; the CCB published no news item specific to 9 November 2023 (its 13 October 2023 item covers the earlier wave, not this one). Impact limited: short-term disruption (<24h), weighted intensity 1, no data breach. Related rows 321 and 3183 (earlier October 2023 incidents at Belgian institutions) exist only as titles - their case files are not in the run's case folder and no results for them exist in the output directory, so nothing further is stated about them; the earlier October attack on the same sites is taken from the HLN/bruzz reporting opened here. Victim-side origin/break for the availability gap rest on coder inference, capping confidence.