2015 · United Kingdom · O - Public administration and defence · Website disruption by DDoS attack
Analysed 2026-11-06 by Hermes
Open this case in the tool →Website disruption by DDoS attack
No DV evidenced
Alternative: Strategy to Leadership
(1) Strategic expectation at the victim: the NCA runs a high-profile law-enforcement website it itself calls an attractive target, and its doctrine on DDoS exposure was explicit and pre-existing - attacks on it are 'a fact of life', a DDoS is 'a blunt form of attack which takes volume and not skill', and the agency stated it has a duty to balance the value of keeping the website accessible against the cost, 'especially in the face of a threat which can scale up endlessly', with measures that restore service generally within 30 minutes. (2) What happened in practice: on 01-09-2015 Lizard Squad used its Lizard Stresser flood service to take the public website offline in apparent revenge for the Operation Vivarium arrests of its customers; the NCA confirmed during the incident that there 'isn't hacking, there's been no intrusion', operations were unaffected, no data was taken, and the site was back the same morning (the agency's own statement anticipates that restoration 'occasionally can take longer'; Ars Technica, citing Sky News, reported over two hours for this episode). The agency published a candid public explanation within hours and had been tweeting DDoS-protection advice for website operators immediately before the attack. (3) Why this is alignment rather than a knowing-doing or doctrinal-material gap: every element of the framework is present on the victim's side and consistent - the threat was identified and analysed before the incident (not a blind spot), the residual gap (temporary loss of website availability) was accepted deliberately, publicly and with an explicit, accountable cost trade-off, and the realised outcome matched the stated capability, so the public account is not contradicted by the documented timeline. Across the lifecycle: entry (volumetric flood against an intentionally public service, no intrusion), containment (blast radius limited to the website; operational capability unaffected), detection (outage recognised immediately and confirmed the same morning), egress (not in play: no intrusion, no data theft), recovery (restored the same morning within the stated standard), response (prompt, accurate public clarification; disclosure duty not triggered, no personal data involved). Positive evidence of doctrine-execution alignment across all six stages makes this a confirmed control case - 'No DV evidenced' rather than Unknown, because the evidence documents the alignment itself rather than merely the absence of bad news.
RM06 — Risk acceptance / exception distortionRM32 — Capacity / availability-protection gapSource caveats: (a) The EuRepoC row labels the attacker 'ISIS Hackergroup Lizard Squad' and the initiator sub-category Terrorist(s); none of the reporting opened for this task supports an ISIS or terrorist link - all of it describes the Lizard Squad DDoS-for-hire group acting in apparent revenge for the Operation Vivarium arrests, and attribution rests solely on the group's own Twitter posts. (b) The case file's 'disrupted for 30 Minutes' reproduces the NCA's generic statement that the site is 'generally' back within 30 minutes; Ars Technica, citing Sky News, reported over two hours of downtime for this episode. (c) RM06 is coded as the standing risk-acceptance condition the evidence shows: an informed, authorised and publicly justified acceptance of recurring DDoS downtime with recovery-focused compensating measures and no documented expiry or review date - precisely because this acceptance is explicit, reasoned and proportionate, the case reads as an aligned control case rather than a DV-Type. RM32 records the condition that actually manifested: availability protection did not keep the public website up under a volumetric flood, by design. (d) No regulator, parliamentary or formal investigation of this incident was found. Link check: computing.co.uk blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no action required user consent; no restricted sources used.