What happened
Replaying the Illuminate Education December 2021 intrusion
- 1
Keys left behind
April 2018 to December 28, 2021A departed administrator's access key stays active for more than three years; five stolen keys are tried, and AWS accepts that one.
- 2
A new administrator
December 28, 2021 to January 8, 2022, days not statedThe attacker creates a new IAM user that could bypass MFA, changes security groups and resets database passwords.
- 3
Backups out
December 28, 2021 to January 8, 2022787 SQL Server backups, unencrypted at rest, leave AWS with data on more than 10.1 million students; where they went is not stated.
- 4
Deletion and ransom
January 8, 2022Database resources are deleted and the sites go down; staff terminate the access within hours, and a ransom demand follows.
According to the regulators, the attackers held the AWS account of Illuminate's school products for 13 days, took unencrypted database backups with personal information of more than 10.1 million students, deleted database resources and were paid a ransom; not all data was returned.
Where cloud-provider controls fit
A service control policy that refuses IAM user calls without MFA would have bounded the former administrator's key in a member account of an AWS organization, and one that refuses calls from outside your networks would have bounded where the key worked. Service control policies on IAM user creation, security group changes and database deletion would have bounded the steps that followed. A customer managed AWS KMS key whose key policy names only the backup and restore roles would have kept the backups sealed to the attacker's credentials, and AWS Backup Vault Lock would have kept recovery points that cannot be deleted. Every service control policy here depends on the account being a member of an AWS organization, which the sources do not state. Removing a departed employee's keys and keeping keys out of source code stay with you on every cloud.
Could this have been prevented?
In hindsight, no control would have stopped it. 9 controls would have limited how far it went. 2 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.
- 0
- Prevented
- 9
- Contained
- 2
- 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.
Replaying the Illuminate Education December 2021 intrusion
1 · Keys left behind
3 Contained2 Not covered6 on other clouds2 · A new administrator
2 Contained6 on other clouds3 · Backups out
2 Contained3 on other clouds4 · Deletion and ransom
2 Contained3 on other cloudsKey facts
- The access key pair of an IAM user with administrator privileges stayed active after its owner left in April 2018 and was never disabled or rotated, the FTC alleges
- Over December 27 and 28, 2021 the attackers tried five sets of stolen access keys; three of the five had once been hardcoded in source code in an online repository, and how the keys were obtained was not determined (NYAG)
- GuardDuty, enabled on a limited basis, raised 44 findings tied to the attackers between December 27, 2021 and January 2, 2022, and nobody reviewed them (NYAG)
- The attackers exfiltrated database backups, 787 SQL Server backups per the FTC and hundreds per the NYAG, unencrypted at rest, with data on more than 10.1 million students
- On January 8, 2022 the attackers deleted database resources; staff identified the compromised credentials and terminated the access within hours
- Illuminate paid an undisclosed ransom and not all data was returned (FTC); New York, California and Connecticut announced $5.1 million in settlements on November 6, 2025
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.In the Matter of Illuminate Education, Inc.: Complaint (FTC File No. 222-3105), as released with the proposed consent orderFederal Trade Commission · Dec 1, 2025 · AdvisoryThe allegations: the AWS services of the school products, unencrypted student data and backups, the former employee's IAM administrator key pair left active since April 2018 and never rotated, the five credential sets, the token and the new user that could bypass MFA, the security group, password and deletion actions, the 787 SQL Server backups, the 13 days, the alert on January 8, 2022, the ransom, the GuardDuty configuration, SSO and MFA not enforced until April 2022, and the more than 10.1 million students
- 2.In the Matter of Illuminate Education, Inc.: Assurance of Discontinuance No. 25-057Office of the New York State Attorney General · Nov 6, 2025 · AdvisoryThe findings: probing on December 27 and 28 with five sets of stolen access keys, the fifth key of a long-departed employee, three keys once hardcoded in source code in an online repository, the key origin undetermined, hundreds of unencrypted database backups exfiltrated, 44 GuardDuty findings not reviewed, the deletion on January 8, the credentials disabled within hours, about 1.7 million New York students and the post-breach IAM changes
- 3.Attorney General Bonta Joins States in Securing $5.1 Million in Settlements from Education Software Company for Failing to Protect Students' DataCalifornia Department of Justice, Office of the Attorney General · Nov 6, 2025 · AdvisoryFormer employee credentials in December 2021, new credentials created for future access, backups not kept apart from the active databases, about three million California students and the $5.1 million in settlements
- 4.Attorney General James and Multistate Coalition Secure $5.1 Million from Education Software Company for Failing to Protect Students' DataOffice of the New York State Attorney General · Nov 6, 2025 · AdvisoryFormer employee credentials, unencrypted database files downloaded, 1.7 million New York students in about 750 schools and the $5.1 million settlement
- 5.FTC Takes Action Against Education Technology Provider for Failing to Secure Students' Personal DataFederal Trade Commission · Dec 1, 2025 · AdvisoryFormer employee credentials, a third-party cloud provider, about 10.1 million students, the January 2020 vendor warning and the proposed consent order
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.