EpiSource
bd_2b5d69aa74007bf3 · schema v1 · pii pii-v1
Full breach record for EpiSource →4 incidents on fileEpisource reported to HHS on 2023-06-02 a Hacking/IT Incident affecting 23,557 individuals. Breached information located on Network Server. The cyber-attack compromised PHI including names, DOB, addresses, MRNs, insurance info, diagnoses, and treatment data.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 2, 2023
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?Regulatory filings (3) · sorted by filing gap
- California State AGbd_ba99421fd948eec92023-06-02Verified
- Montana State AGbd_278e1dec2e1b4e362023-06-09 · +7dVerified
- Oregon State AGbd_e609d81cc43fbf8f2023-06-09 · +7dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Jun 2 (CA), last Jun 9 (OR) — 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.