← Breach analysis by the Dual Vulnerabilities framework

berlin.de DDoS outage (Unattributed, 2023)

2023 · Germany · O - Public administration and defence · DDoS attack causing temporary portal outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS attack causing temporary portal outage

Dual vulnerability type

Expertise to Execution

Evidence coverage: 1/6 stages, weight 6/60

Decisive stage: response (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The expectation at the victim was availability: berlin.de is the capital portal through which the State of Berlin delivers information and digital citizen services, so keeping it reachable under foreseeable load, including DDoS pressure, is a baseline operational duty of the state's IT operations; the victim's own April 2023 communication asserted that its protective measures worked. (2) In practice, on 19 September 2023 multiple DDoS waves took the portal completely offline for the 10:30-11:20 window, then degraded it further, with restrictions persisting after disclosure; no data were lost and no infiltration occurred, so the harm was purely an availability failure of the public portal. (3) This is a knowing-doing gap inside the material column: the relevant remedy (DDoS mitigation, capacity and redundancy for the portal) is ordinary technical practice, the threat class was already known to the organisation - it had publicly described the April 2023 attack as the largest yet on its websites and its own September release notes that DDoS attacks are sustained rather than one-off events - yet five months later the same kind of flood again brought the capital portal down. No source documents the internal decision chain, so origin (material: known technical remedy) and break (execution: not realised in operations/architecture rather than a documented leadership deferral) rest on inference from the documented facts; the classification rests on the response stage (availability protection under attack), and the entry vector is not load-bearing - there was no intrusion at all. (4) RM32 (Expertise to Execution lens): the portal's services could not be scaled or protected against the flood because the architecture and protection arrangements in place could not absorb the attack volume, turning a known technical remedy into a five-minute complete outage plus hours of degradation (causal role: Enabling). RM21 (Expertise to Execution lens): the April 2023 DDoS was an earlier comparable, officially documented incident, yet the same overload weakness was evidently not remediated and validated before 19 September 2023, so the known remedy remained unimplemented and the weakness recurred (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; the case-file source_url (Senate Chancellery press release of 19.09.2023) was opened and confirms the incident, timing and no-exfiltration finding. The attack is unattributed and follow-up reporting specifically on the 19 September incident is thin beyond same-day press coverage; reporting on the 2023 DDoS wave (April) quotes State Secretary Kleindiek saying protective measures worked and the internal state network was unaffected. An August 2023 outage of state online services was explicitly not attributed to a hacker attack and is therefore not counted as a comparable earlier incident for RM21. Origin/break of the decisive gap rest on inference because no source documents the victim's internal decision chain; no consent-gated actions were needed.