County of Southampton, Virginia reported a data breach to the Montana Attorney General. The breach was reported on 2022-11-21. The breach occurred on 9/6/2022. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Nov 21, 2022 → Nov 22, 2022. View entity profile → Other incidents for this victim →
incident inc_8743d6b600f24887 · merge_method deterministic · 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
Sep 6, 2022
When the intrusion reportedly occurred, per the linked filings
Sep 14, 2022
Reported by MAINE AG filing
County of Southampton, Virginia reported a data breach to the Montana Attorney General. The breach was reported on 2022-11-21. The breach occurred on 9/6/2022. 2 Montana residents were affected.
Affected (this filing): 2
Southampton County, Virginia, a government entity, reported an external system breach that occurred on September 6, 2022, and was discovered on September 14, 2022. The breach affected 11,235 individuals, compromising names and driver's license or non-driver ID card numbers. Notifications were sent to affected individuals on November 22, 2022, along with an offer of one year of identity theft protection services from Experian.
Affected (this filing): 11,235
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.