McKissock Investment Holdings, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-05-01. The breach occurred from 11/16/2019 to 3/4/2020. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filed May 1, 2020. View entity profile → Other incidents for this victim →
incident inc_c154ff49ff344901 · merge_method deterministic · confidence 100%
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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 16, 2019
When the intrusion reportedly occurred, per the linked filings
McKissock Investment Holdings, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-05-01. The breach occurred from 11/16/2019 to 3/4/2020. 2 Montana residents were affected.
Affected (this filing): 2
McKissock Investment Holdings, LLC notified the California AG of unauthorized access to a legacy virtual server between November 16, 2019 and March 4, 2020. The affected data included names and driver's license or state identification numbers. The incident was discovered on or about March 26, 2020 when a data review confirmed personal information was present. McKissock disabled access to the server, engaged forensic investigators, and offered 12 months of NortonLifeLock identity monitoring to affected individuals.
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.