The Southwestern Family of Companies reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-01. The breach occurred from 11/1/2021 to 11/30/2021. 14 Montana residents were affected.
Affected (this filing): 14
Clustered 2 filings across 2 jurisdictions · filed Aug 1, 2022. View entity profile → Other incidents for this victim →
incident inc_d5fd3ebe27ef4c51 · 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
Nov 1, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 1, 2022
Reported by MAINE AG filing
The Southwestern Family of Companies reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-01. The breach occurred from 11/1/2021 to 11/30/2021. 14 Montana residents were affected.
Affected (this filing): 14
The Southwestern Family of Companies experienced a ransomware incident on November 17, 2021, which was discovered on March 1, 2022. The breach compromised the names and Social Security numbers of 7,170 individuals, including 17 Maine residents. The company provided written notification to affected individuals on August 1, 2022, and offered 12 months of complimentary credit monitoring and identity restoration services through Equifax.
Affected (this filing): 17
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.