Gibson Insurance Agency reported a data breach to the Montana Attorney General. The breach was reported on 2016-10-14. The breach occurred on 7/28/2016. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Oct 14, 2016. View entity profile → Other incidents for this victim →
incident inc_58a7760635674268 · 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.
IN MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 28, 2016
When the intrusion reportedly occurred, per the linked filings
Jul 28, 2016
Reported by HHS OCR filing
Gibson Insurance Agency reported a data breach to the Montana Attorney General. The breach was reported on 2016-10-14. The breach occurred on 7/28/2016. 1 Montana residents were affected.
Affected (this filing): 1
Gibson Insurance Agency, Inc. reported to HHS on 2016-10-14 a Theft affecting 7242 individuals. Breached information located on Laptop. An employee's laptop was stolen from her car on July 28, 2016, potentially containing demographic and health insurance information. The covered entity notified HHS, individuals, and media, investigated, sanctioned the employee, and implemented safeguards including encryption, security management systems, complex passwords, and automatic logoff.
Affected (this filing): 7,242
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.