Baltimore City Public Schools
bd_9ab6c0fe1104bebb · schema v1 · pii pii-v1
Full breach record for Baltimore City Public Schools →Baltimore City Public Schools experienced a cybersecurity incident on February 13, 2025, where files containing names and other data elements were taken from their network. The investigation confirmed the involvement of personal information. The organization notified law enforcement, engaged external cybersecurity experts, and implemented remediation measures including endpoint detection and response software and password resets. Affected individuals are offered two years of complimentary credit and identity monitoring services.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 13, 2025
Begins
Apr 29, 2025
Filed
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Massachusetts State AGbd_b126e5260febdbd02025-04-29Verified
- Maine State AGbd_bb5f9b0432bd4ec52025-04-29Candidate
- New Hampshire State AGbd_da05d89cd8b7eef72025-04-29Verified
- Idaho State AGbd_e3c3ec5edab659912025-04-28 · +1dCandidate
Show 2 more filings ↓Show fewer ↑up to 5d gap
- Indiana State AGbd_1aa674a0a361f7e32025-04-24 · +5dVerified
- Nebraska State AGbd_313c761c5298f2b22025-04-24 · +5dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Apr 24 (IN), last Apr 29 (VT) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.