EpiSource
bd_278e1dec2e1b4e36 · schema v1 · pii pii-v1
Full breach record for EpiSource →4 incidents on fileEpisource, a medical coding vendor, notified Montana residents of a data breach involving unauthorized access to its AWS environment between Feb 19-21, 2023. Suspicious activity was detected on Feb 20, 2023. Compromised data included names, DOBs, addresses, MRNs, and clinical data. No SSNs or financial data were involved. Episource engaged forensic investigators, hardened AWS security, and offered one year of LifeLock identity theft protection.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 19, 2023
Begins
Feb 20, 2023
Discovered
Jun 9, 2023
Filed
vs. sector median
+5 wks slower
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Oregon State AGbd_e609d81cc43fbf8f2023-06-09Verified
- HHS OCRbd_2b5d69aa74007bf32023-06-02 · +7dVerified
- California State AGbd_ba99421fd948eec92023-06-02 · +7dVerified
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Jun 2 (MN), last Jun 9 (MT) — 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.