Cierant
bd_af70698266095000 · schema v1 · pii pii-v1
Full breach record for Cierant →Cierant Corporation reported to HHS on 2025-07-03 a Hacking/IT Incident affecting 232506 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
Jul 3, 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 (1)
- Leak Sitecl0pbd_07daf6a1b38451a92025-02-01 · +151dVerified by operator
Regulatory filings (7) · sorted by filing gap
- Illinois State AGbd_f1e6a8237f126a062025-07-01 · +2dCandidate
- Montana State AGbd_154646e20b01c5db2025-07-07 · +4dVerified
- Washington State AGbd_15d0ae25a9674afd2025-07-07 · +4dVerified
- Washington State AGbd_3dde15084b7b9d422025-07-07 · +4dVerified
Show 3 more filings ↓Show fewer ↑up to 5d gap
- Montana State AGbd_d4221b679ab06c8d2025-07-07 · +4dVerified
- California State AGbd_dc825fbbaeb958ce2025-07-07 · +4dVerified
- Texas State AGbd_a2f1dac33b9456df2025-07-08 · +5dVerified
Filing propagation · 8 filings · 6 states
View merged incident ↗Pattern: first filing Jul 1 (IL), last Jul 8 (TX) — a 7-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.