2012 · United Kingdom · J - Information and communication · Denial-of-service attack on internal e-mail and internet systems
Analysed 2026-11-07 by Hermes
Open this case in the tool →Denial-of-service attack on internal e-mail and internet systems
No DV evidenced
Alternative: none defensible
(1) The strategic expectation at the BBC was continuity of its broadcast and internal communications: Director-General Mark Thompson stated publicly that the corporation was taking every step it could to keep the Persian Service running, and the BBC is a national broadcaster with a standing availability expectation around its London headquarters. (2) What the record shows in practice is narrow: around 1-2 March 2012 the BBC's London HQ sustained a flood-type attack, understood to be a distributed denial-of-service attack, that left some parts of the corporation unable to access internal e-mail and other internet services for roughly four hours, with internal communications problems continuing into the following week; on-air output was unaffected, no data was taken, and the attack coincided with attempts to jam two BBC Persian satellite feeds into Iran and to swamp the Service's London phone lines with automated calls (Guardian; BBC News). The BBC disclosed the incident itself on 14 March 2012 via Thompson's Royal Television Society speech but withheld all operational detail, citing an ongoing investigation, and stated that confirming the source of the attacks was difficult and might prove impossible. (3) The DV framework requires a documented victim-side gap: an expectation or known remedy (origin) and the point where the chain broke (break). No source - press, regulator, CERT or the BBC's own statements - documents the BBC's availability arrangements, capacity or mitigation decisions, any expert warning, or any policy that was not executed, and no formal investigation reviewed the incident; the victim itself deliberately kept the mechanism undisclosed. Reporting therefore confirms impact only, which is the method spec's decision-rule case for Unknown; reading the four-hour disruption back as an Expertise to Execution capacity gap would be exactly the rejected reasoning from the attacker's technique and would rest wholly on the coder's own inference. The entry technique (DDoS) is not load-bearing for a DV reading, and the co-ordinated jamming and phone-line flooding show this sits close to the atypical state-pressure-campaign category: pressure on a broadcaster's output rather than an organisation's security gap exploited. The one directly evidenced victim-side condition - internal e-mail and internet services could not stay available under the flood - is recorded as RM32 without a DV lens sentence (Unknown).
RM32 — Capacity / availability-protection gapData quality: the row carries no receiver_name and the name field 'Guardian on Iranian cyber-attack' is the source article's title (The Guardian is the reporter, not the victim); the victim was derived from the description and is the BBC. Date discrepancy: BBC News reports the outage on 1 March, The Guardian and the case start_date (02.03.2012) on 2 March; Year taken as 2012 either way. Attribution is suspicion only: the victim attributes ('receiver attributes attacker' in eurepoc_extra), and Thompson himself said confirming the source 'may prove impossible'; no state or CERT ever confirmed Iranian responsibility. Disclosure: victim-disclosed on 14 March 2012 (RTS speech); the BBC deliberately withheld detail pending an investigation, which is why no lifecycle stage beyond the impact is documented. Earlier assaults on the BBC are mentioned ('a widening of earlier assaults'; jamming of BBC Persian since 2009), but no source documents an earlier comparable weakness that was analysed and left unremediated, so RM21 was not coded. Impact per the case file: disruption under 24h, weighted intensity 1, no data theft. No related_rows in the case file. Unattended run: no consent-gated actions were needed.