2023 · Finland · O - Public administration and defence · Distributed denial-of-service attack (short service disruption)
Analysed 2026-11-06 by Hermes
Open this case in the tool →Distributed denial-of-service attack (short service disruption)
No DV evidenced
Alternative: Strategy to Execution
(1) Strategic expectation: as the Finnish state agency running nationwide electronic services (vehicle registration, traffic permits, licensing, the NCSC-FI itself), Traficom carried a public-sector continuity expectation for service availability and an institutionalised DDoS preparedness posture - its own cyber security centre publishes national denial-of-service response guidance and treats DDoS mitigation as daily routine. (2) Practice: on 23 September 2023 the third flood attack of the month briefly blocked Traficom's electronic services; mitigation measures were activated immediately, the agency disclosed the attack on its official X channel that morning, advised alternative channels (insurance companies' registration services) for urgent matters, the fault was resolved around noon and Traficom announced the services working again the same day; no data breach, data corruption or economic impact is documented (EuRepoC intensity 1, disruption under 24h). (3) Reviewed across the lifecycle, the evidence shows alignment rather than a gap: the doctrinal artefact (DDoS preparedness and response guidance) demonstrably translated into operational execution - NCSC-FI reported the September attacks successfully thwarted, critical services restored quickly and other services secured with backup procedures, and explicitly noted that no complete protection against DDoS exists; the response was accurate and same-day, so the public account matches the documented impact timeline. No source documents a victim-side omission, an unremediated known weakness, a delayed response or a contradicted narrative, so neither the knowing-doing nor the doctrinal-material test is met; the classification rests on the recovery and response/disclosure stages, and the entry vector (flood traffic against public web services) is not a victim-side condition and not load-bearing. Coded markers record conditions the evidence shows, without asserting a DV gap: RM32 - availability protection bounded but could not fully hold the public e-services up under flood load (the 23 September outage lasted a few hours); RM04 - the electronic-transaction portfolio rides on shared public web infrastructure, so a single attack took all e-transaction services down at once and manual fallback (insurance companies' digital services) carried urgent transactions.
RM32 — Capacity / availability-protection gapRM04 — Control dependency concentrationDataset actor is Not attributed; NCSC-FI publicly attributed the 7 and 18 September traficom.fi attacks to pro-Russian hacktivist group NoName / NoName057(16) (motivation: Finland's ban on Russian-registered cars), and the 23 September attack was claimed by NoName057(16) as reported by RBC-Ukraine - an attacker claim, unconfirmed by the Finnish authorities for that date. The 23 September event was the third disruption of September 2023 (7 and 18 September preceded it); the row covers only the 23 September disruption, and NCSC-FI's public record shows no earlier comparable unremediated weakness, so no recurring-weakness marker is coded. Iltalehti article body was only partially extractable (title and lead confirm this was another (jalleen) DDoS against Traficom). Unattributed actor does not lower the confidence (DV is assessed victim-side). No DV evidenced rests on positive alignment evidence from the victim's own X disclosure and NCSC-FI's weekly reviews, not on absence of bad news. Unattended run: nothing required consent.