TEAM Software
bd_8e13e6dc5d6476b6 · schema v1 · pii pii-v1
Full breach record for TEAM Software →TEAM Software detected unusual activity on July 26, 2024, leading to the discovery that an unauthorized actor accessed certain systems between July 25 and July 26, 2024. The incident potentially exposed names and other data elements. The company engaged third-party forensics, strengthened security, and offered credit monitoring. This is a supplemental notice to the California Attorney General.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 25, 2024
Begins
Jul 26, 2024
Discovered
Nov 12, 2024
Filed
vs. sector median
+5 wks slower
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Maine State AGbd_29759b90d61ff1e12024-11-12Candidate
- Vermont State AGbd_57c96ec86ce7f41b2024-11-12Verified
- Oregon State AGbd_6d55adc4eb06f0052024-11-12Verified
- Washington State AGbd_6f15b94c23a0e4a02024-11-12Verified
Show 5 more filings ↓Show fewer ↑up to 19d gap
- Illinois State AGbd_688d8046f7003f772024-11-01 · +11dVerified
- Massachusetts State AGbd_5410d249da439f7e2024-10-25 · +18dVerified
- California State AGbd_2d22036cb19206d12024-10-24 · +19dVerified
- Montana State AGbd_3be93185868325eb2024-10-24 · +19dVerified
- Indiana State AGbd_83a6a19cc4362ab22024-10-24 · +19dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing Oct 24 (CA), last Nov 12 (CA) — a 19-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.