UConn Health reported a data breach to the Montana Attorney General. The breach was reported on 2019-02-21. The breach occurred from 8/20/2018 to 8/27/2018. 17 Montana residents were affected.
Affected (this filing): 17
Clustered 2 filings across 2 jurisdictions · filing window Feb 21, 2019 → Feb 22, 2019. View entity profile → Other incidents for this victim →
incident inc_eab7e00d4dcf4c23 · merge_method deterministic · confidence 100%
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 20, 2018
When the intrusion reportedly occurred, per the linked filings
UConn Health reported a data breach to the Montana Attorney General. The breach was reported on 2019-02-21. The breach occurred from 8/20/2018 to 8/27/2018. 17 Montana residents were affected.
Affected (this filing): 17
UConn Health notified affected individuals of unauthorized access to a limited number of employee email accounts between August 20–27, 2018. The investigation determined on December 24, 2018 that the accounts contained personal information including names, SSNs, addresses, dates of birth, driver's license numbers, and medical information. Approximately 504 Rhode Island residents were affected. UConn Health secured accounts, notified law enforcement, and retained a forensic security firm.
Affected (this filing): 504
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.