Clustered 2 filings across 2 jurisdictions · filed May 16, 2023. View entity profile → Other incidents for this victim →
incident inc_49e89291bcea466b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Financial account
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 NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 14, 2023
When the intrusion reportedly occurred, per the linked filings
Mar 5, 2023
Reported by CALIFORNIA AG, NEW HAMPSHIRE AG filings
Sysco Corporation disclosed a cybersecurity event where an unauthorized threat actor gained access to systems starting January 14, 2023, detected on March 5, 2023. Personal information of current and former colleagues, including names, SSNs, and account numbers, was potentially compromised. Sysco engaged forensic experts, notified law enforcement, and offered 24 months of identity protection.
Sysco Corporation notified the NH AG of a cybersecurity event where an external threat actor gained unauthorized access to systems starting Jan 14, 2023. Discovered March 5, 2023, the incident likely involved PII of employees and limited customer/supplier data. 199 NH residents were notified. Sysco engaged forensic professionals, contacted law enforcement, and offered 24 months of credit monitoring via Experian.
Affected (this filing): 199
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.