City of Torrance
bd_16c8e764e7e05e93 · schema v1 · pii pii-v1
Full breach record for City of Torrance →On March 1, 2020, the City of Torrance, California experienced a cybersecurity incident affecting some of its computer systems. During the investigation, the City determined that data taken during the incident was accessible on the internet. On August 4, 2020, it was confirmed that one or more compromised documents may contain affected individuals' names. The City deployed security enhancements and offered one-year Experian IdentityWorks Credit 3B memberships to affected individuals. Notification letters were sent October 9, 2020.
J jump to incidentP pin to compareR raw source
Incident timeline
Mar 1, 2020
Begins
Oct 18, 2020
Filed
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitedoppelpaymerbd_d82eb43ce1b2e1632020-03-01 · +231dVerified by operator
Regulatory filings (6) · sorted by filing gap
- Maine State AGbd_2b3c67d52d445c282020-10-18Verified by operator
- New Hampshire State AGbd_0c4c959bdeea15ee2020-10-21 · +3dVerified by operator
- Indiana State AGbd_8a88b781f105a6662020-10-13 · +5dVerified by operator
- Montana State AGbd_af935553dc09ee0b2020-10-13 · +5dVerified by operator
Show 2 more filings ↓Show fewer ↑up to 153d gap
- Massachusetts State AGbd_1ff21cd8deb6825d2020-05-20 · +151dVerified
- California State AGbd_d8ff1381ca0cea972020-05-18 · +153dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing May 18 (CA), last Oct 21 (NH) — a 156-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.