Clustered 2 filings across 2 jurisdictions · filing window Aug 25, 2020 → May 10, 2021. View entity profile → Other incidents for this victim →
incident inc_6bbf244f476246ee · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Employment
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.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 14, 2020
When the intrusion reportedly occurred, per the linked filings
Jul 28, 2020
Reported by CALIFORNIA AG, MAINE AG filings
Brown-Forman Corporation disclosed a cyber attack where criminals stole records containing personal information of current and former employees, including SSNs, home addresses, and salary data. Suspicious activity was discovered on July 28, 2020. The company engaged forensic experts, contained the breach, and offered one year of credit monitoring.
Brown-Forman Corporation experienced a hacking incident discovered on July 28, 2020. Unauthorized actors stole data from the company's internal network, which was confirmed on August 4, 2020. The breach affected 72 Maine residents, including dependents, beneficiaries, and former employees, exposing their Social Security numbers and, in some cases, expired credit card information. The company provided notice to the affected individuals and offered one year of complimentary credit monitoring services.
Affected (this filing):
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.