What happened
Voova’s hosting environment / The servers supported coach operators.
- 1
Post-contract access
May 17, 2016Voova believed it had removed the contractor’s access. Five days after his contract ended, he returned and inspected account permissions.
- 2
Server deletions
May 18, 2016The next day he used a colleague’s account to terminate 23 AWS-hosted servers. The judge attributed about £500,000 in combined losses to Voova and its customer CoachHire.
Impact
Voova lost UK customers and had no offsite backups. The sentencing judge put the combined loss to Voova and CoachHire at about £500,000.
Could this have been prevented?
Close access when a contract ends
Voova believed it had removed the departing contractor’s access. Confirming that accounts and sessions have been revoked addresses that first gap. Today, an AWS service control policy can also limit where a member account’s credentials can be used. That option became available after this incident. An independent backup can support recovery after a deletion.
Incident control assessments
- 0
- Prevented
- 1
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Voova’s hosting environment / The servers supported coach operators.
1 · Post-contract access
1 Not covered2 · Server deletions
1 ContainedKey facts
- Voova let the contract expire on May 12, 2016. It believed it had removed the former contractor’s own credentials.
- He returned to Voova’s system on May 17 and inspected account permissions.
- The court traced the May 18 deletions to the network of his other employer.
- Voova lost UK customers. The judge’s estimate combined Voova’s loss with that of CoachHire.
- The Court of Appeal upheld the two-year sentence on September 3, 2019.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.R v Needham [2019] EWCA Crim 1541Court of Appeal of England and Wales · Sep 3, 2019 · AdvisoryParagraphs 3–9 and 12–16 cover both days of access, attribution, losses and the lack of offsite backups.
- 2.Court report on the alleged deletion of Voova’s serversDaily Mirror · Jan 22, 2019 · NewsThe allegations about the May 2016 AWS incident were public by January 22, 2019.
- 3.Vengeful sacked IT bod destroyed ex-employer's AWS cloud accountsThe Register · Mar 20, 2019 · NewsAWS login of a former colleague, password change, instances terminated, multi-factor authentication not implemented, IP trace, losses, sentence
- 4.Data perimeters on AWSAWS · undated · Vendor reportWhich account identities and network origins a service control policy can restrict.
- 5.Document history for AWS OrganizationsAWS · undated · Vendor reportAWS Organizations launch and introduction of conditional service control policies.
The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.