Kronick Moskovitz Tiedemann & Girard
bd_d2db47f3b9d4421f · schema v1 · pii pii-v1
Full breach record for Kronick Moskovitz Tiedemann & Girard →5 incidents on fileKronick Moskovitz Tiedemann & Girard reported to HHS on 2025-02-28 a Hacking/IT Incident affecting 2511 individuals. Breached information located on Network Server. Business Associate present.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Feb 28, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siterhysidabd_485be91e1544288f2024-08-22 · +189dVerified
- Leak Siterhysidabd_5115b8f34c4643132024-08-06 · +206dVerified by operator
Regulatory filings (6) · sorted by filing gap
- California State AGbd_f96d420733a272eb2025-02-28Verified by operator
- California State AGbd_3b9c18091611fea22025-03-28 · +28dVerified by operator
- Vermont State AGbd_78a8971981b2e05c2025-03-28 · +28dVerified by operator
- Indiana State AGbd_85953c04009ba2202025-03-28 · +28dVerified
Show 2 more filings ↓Show fewer ↑up to 91d gap
- Massachusetts State AGbd_09dc26c198a885a62025-01-27 · +32dVerified by operator
- California State AGbd_26e21b83d173f48c2025-05-30 · +91dVerified
Filing propagation · 7 filings · 4 states
View merged incident ↗Pattern: first filing Jan 27 (MA), last May 30 (CA) — a 123-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.