Rock County Human Services Department reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-12. The breach occurred from 2/28/2022 to 6/14/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Sep 12, 2022 → Sep 21, 2022. View entity profile → Other incidents for this victim →
incident inc_4eba27393aca44cf · merge_method human · confidence 100%
Discovered → first regulatory filing
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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 28, 2022
When the intrusion reportedly occurred, per the linked filings
Jun 14, 2022
Reported by MAINE AG filing
Rock County Human Services Department reported a data breach to the Montana Attorney General. The breach was reported on 2022-09-12. The breach occurred from 2/28/2022 to 6/14/2022. 1 Montana residents were affected.
Affected (this filing): 1
Rock County Human Services Department, a government entity, experienced an external system breach (hacking) on February 28, 2022, which was discovered on June 14, 2022. The breach affected 25,610 individuals, exposing their names and Social Security numbers. The organization began notifying affected individuals on September 13, 2022, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 25,610
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.