What was exposed
Replaying the Schoolzilla April 2017 exposure
- 1
Configured: database backups in a bucket open to the internet
Not stated; before April 4, 2017Schoolzilla's backup settings write personal information from its data warehousing tools to the S3 bucket sz-backups, which is configured for public access; which setting opened it, who set it and since when are not stated.
- 2
Reachable: student records in backups up to 12 GB
Until on or about April 5, 2017; start not statedAnyone who knows the bucket's name can download its production backups with no credential mentioned, the largest about 12 GB: partial student records of current and former customers, with usernames and passwords for one network.
- 3
Found and closed: fixed on or about April 5, 2017
On or about April 4 to 5, 2017The finder reaches sz-backups by trying name variants after sz.tableau, downloads several backups and reports them; Schoolzilla fixes the error on or about April 5, 2017, the day it receives the notice, and how the bucket was closed is not stated.
Production database backups, the largest about 12 GB, with partial student records of multiple school districts and charter networks, among them student usernames with passwords for one network and the data of a former customer, could be downloaded from the internet until on or about April 5, 2017; when the exposure began is not stated, and Schoolzilla says its logs show no access other than the finder's.
Where cloud-provider controls fit
Amazon S3 Block Public Access on the account, or set for every account by an organization policy, would have refused the setting that opened your backup bucket, whether an ACL or a bucket policy carried it. Object Ownership would have closed the ACL path only, and a service control policy would have kept ACL and bucket policy writes to approved administrators. While the bucket stood open, a resource control policy written to refuse anonymous and outside-organization S3 requests, or the IgnorePublicAcls and RestrictPublicBuckets settings of the same block, would have kept a reader outside your account from downloading the backups. Each of these, in the form described, dates from after this exposure. Azure refuses the opening with its anonymous-access account setting, Google Cloud with the public access prevention constraint, and Oracle Cloud with a Security Zone, which does not close a bucket that is already public. Finding an open bucket and closing it stay the owner's job: the provider's checks report such a bucket rather than refuse it.
Could this have been prevented?
In hindsight, not as a whole. 1 control would have refused a step outright, and 4 controls would have limited one. 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.
- 1
- Prevented
- 4
- 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 Schoolzilla April 2017 exposure
1 · Configured: database backups in a bucket open to the internet
1 Prevented2 Contained3 on other clouds2 · Reachable: student records in backups up to 12 GB
2 Contained3 on other clouds3 · Found and closed: fixed on or about April 5, 2017
2 Not coveredKey facts
- Schoolzilla's data configuration settings backed up personal information from its data warehousing tools to the Amazon S3 bucket sz-backups, which was configured for public access; which setting opened it, who set it and when were not stated, and Schoolzilla declined to say how long it lasted
- The finder found an exposed bucket named sz.tableau while looking at Tableau-related buckets, then found sz-backups by trying other sz name variants; what sz.tableau held and whether he read it were not stated
- He downloaded several production database backups, the largest, Web_Data_FULL, about 12 GB, and loaded them into a local MSSQL instance, which showed real student data
- The backups held partial student records of multiple school districts and charter networks; for Alliance College-Ready Public Schools they could include student usernames with the associated passwords, contact, health, special education and test data, and Palo Alto Unified counted about 14,000 current and former students as of April 20, 2017, data kept after its contract ended in May 2016
- The finder reported children's Social Security numbers in the data; Palo Alto Unified said none of its students' numbers were exposed because it collects none. The finder estimated that 1.3 million students may have been exposed, as of April 20, 2017, per EdSurge, and no source gave a confirmed total
- A researcher detected the vulnerability on or about April 4, 2017, and Schoolzilla fixed the error on or about April 5, the day it received the notice; the researcher deleted his copies within a day and signed an affidavit, and Schoolzilla said its logs showed no access other than his
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.22 Data Breaches We Found and Reported in 2017 (section: Schoolhouse data breach)MacKeeper (MacKeeper Security Research Center) · Feb 19, 2026 · Researchthe finder's first-person account: S3 bucket configured for public access, the buckets sz.tableau and sz-backups, discovery by name variants, several production backups downloaded, largest backup Web_Data_FULL about 12 GB, local MSSQL load, data types including children's Social Security numbers as he describes them, deletion of his copies, Schoolzilla's response and the CEO's calls
- 2.Notice of Data BreachAlliance College-Ready Public Schools (filed with the California Attorney General) · Jun 30, 2017 · Vendor reportdetection on or about April 4, 2017, notice received and error fixed on or about April 5, 2017, multiple school districts and charter networks affected, record types of that network's students including usernames with passwords, logs showing no other access, deletion within a day, affidavit, reconfiguration and password changes, third-party security experts
- 3.Schoolzilla 'File Configuration Error' Exposes Data for More Than 1.3M Students, StaffEdSurge · Apr 20, 2017 · Newsbackups written by Schoolzilla's data configuration settings to a publicly accessible location on Amazon S3, largest backup 12 GB, the finder's estimate of 1.3 million students as of April 20, 2017, Palo Alto count of 14,000, a Texas charter school network affected, CEO statement, server records and affidavit, duration not disclosed
- 4.Schoolzilla Security Issue Exposes Data for 1.3 Million Students and StaffTHE Journal · Apr 21, 2017 · Newsmore than 1.3 million students, parents, teachers and administrators told their information was vulnerable as of April 21, 2017, CEO statement that the error was fixed immediately
- 5.Private student data temporarily leakedThe Campanile (Palo Alto High School) · Apr 26, 2017 · NewsPalo Alto Unified announcement on April 20, 2017 of about 14,000 current and former students, record types, no Social Security numbers collected, contract ended in May 2016 with the data still held, district CTO's account of Schoolzilla's logs
The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.