2023 · Netherlands · R - Arts, entertainment and recreation · Ransomware intrusion with data theft and ransom payment (double extortion)
Analysed 2026-11-07 by Hermes
Open this case in the tool →Ransomware intrusion with data theft and ransom payment (double extortion)
Strategy to Leadership
Evidence coverage: 2/6 stages, weight 13/60
Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution
(1) As the national football association the KNVB holds highly sensitive personal data on members, players, referees and claimants - identity documents, signatures, salary and bank data, medical records of the Sports Medical Centre and disciplinary files from 1999-2020 - so the strategic expectation was GDPR-grade protection, timely and complete notification of affected individuals, and the forensic readiness to tell victims what was actually taken. (2) Operationally, the LockBit double-extortion intrusion discovered on 1 April 2023 produced an exfiltration that the victim itself could never scope (Fox-IT found only a limited number of digital traces), while the ransom demand was settled 'onder deskundige begeleiding' with a publication/deletion agreement; the April public record said employees' data, no notable disruption, and denied the reported phishing entry and 300 GB encryption; only on 12 September 2023 did the KNVB itself disclose that it had paid, that hundreds of gigabytes were taken and which sensitive categories were involved. (3) This is a doctrinal-column gap with a leadership break: the expectation is contained in the KNVB's own public statements and GDPR communication duty, and the chain broke at the decision level - withholding, denial and a roughly five-month silence were strategic communication choices ('om strategische redenen'), and the public account was later corrected by the organisation's own disclosure of the payment and the scale; it is the knowing-doing gap between what leadership knew (extortion negotiation, data at risk) and what it communicated, not generic weak security. The entry vector is not load-bearing and never established; the egress gap (missing forensic traces, material origin, execution break) is documented but contributing, and forms the Expertise to Execution runner-up. The classification rests on the response/disclosure stage. (4) RM33 (Strategy to Leadership lens): forensic readiness was not required by the organisation as part of its incident posture, so Fox-IT had too few digital traces to scope the theft and leadership could only tell over a million potentially affected people that what was taken could not be established (causal role: Obscuring). RM39 (Strategy to Leadership lens): disclosure behaviour diverged from the legal and strategic communication expectation - the AP was notified timely, but individuals received a stripped account for about five months, the April denials were revised by the September statement, and the communication was publicly criticised by security experts and by the chair of the privacy watchdog as slow and insufficient (causal role: Constraining).
RM33 — Logging / forensic-readiness gapRM39 — Breach notification / disclosure failureBlind case file: description n/a and no usable source_url (the field holds the pipeline note 'Insufficient public root-cause source found'); all lifecycle evidence was researched from scratch. Entry vector unestablished: RTL reported a phishing e-mail via KNVB sources (April 2023); the KNVB publicly said it did not recognise that account; the Fox-IT forensic report has never been published. LockBit's 305 GB claim is an attacker claim, cited only as reported by the press; the KNVB's own September statement says hundreds of gigabytes. The ransom payment was documented as decided under expert guidance with a stated rationale, so the RM42 exclusion applies and it is not coded; the AP chair criticised the payment policy itself, not its governance. The Autoriteit Persoonsgegevens was in talks with the KNVB about the protection of personal data (AD, autumn 2023) and a fine was not excluded, but no regulator finding of failings or violation could be established, so neither that rule nor 'No DV evidenced' applies. Associated bodies (Eredivisie CV/CED, FBO archive) were affected via KNVB systems per the victim's own announcement, but no source documents a victim-side containment failure, so no containment marker is coded.