Clustered 2 filings across 2 jurisdictions · filing window Nov 25, 2020 → Nov 30, 2020. View entity profile → Other incidents for this victim →
incident inc_0f59040d78334194 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Government ID · Identity (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 27, 2020
When the intrusion reportedly occurred, per the linked filings
Oct 27, 2020
Reported by MAINE AG, NEW HAMPSHIRE AG filings
USG Insurance Services, Inc. reported an external system breach (hacking) on October 27, 2020, affecting 1,530 individuals, including 6 Maine residents. The breach compromised names and Social Security Numbers. The company provided written notification on November 25, 2020, and offered 12 months of credit monitoring through Kroll.
Affected (this filing): 1,530
USG Insurance Services, Inc. notified the New Hampshire Attorney General of a cybersecurity incident discovered on October 27, 2020. An unauthorized user gained access to a server storing employee PII, potentially affecting 5 NH residents. Data accessed included names, SSNs, driver's licenses, and financial info. USG engaged forensic investigators, implemented Carbon Black security measures, reset passwords, and provided 12 months of credit monitoring.
Affected (this filing): 5
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.