SYSCO CORPORATION
bd_3041dfe2cdc8303f · schema v1 · pii pii-v1
Full breach record for SYSCO CORPORATION →3 incidents on fileSysco Corporation reported a data breach to the Oregon Attorney General. The breach was reported on 2023-05-16. The breach occurred during 1/14/2023 - 3/5/2023. The breach was discovered on 3/5/2023. 126,243 individuals were affected. Notice was sent on 5/5/20235/8/2023.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 14, 2023
Begins
Mar 5, 2023
Discovered
May 16, 2023
Filed
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitedunghillbd_23944c27089111552023-05-27 · +11dVerified by operator
Regulatory filings (9) · sorted by filing gap
- California State AGbd_090a2297858052432023-05-16Verified by operator
- New Hampshire State AGbd_9478a567d0d141412023-05-16Verified by operator
- Massachusetts State AGbd_050ce61aec90f9112023-05-17 · +1dVerified by operator
- Washington State AGbd_44c863a405c6225f2023-05-17 · +1dVerified by operator
Show 5 more filings ↓Show fewer ↑up to 135d gap
- Maine State AGbd_5d5516fe15b8939c2023-05-17 · +1dVerified by operator
- South Carolina State AGbd_a670fc947a726bf32023-05-17 · +1dVerified by operator
- Hawaii State AGbd_e3b3f0b86bc7928e2023-05-17 · +1dVerified by operator
- Indiana State AGbd_cc2a933e586ea52a2023-05-05 · +11dVerified by operator
- Illinois State AGbd_c18a45d8d04a0a202023-01-01 · +135dVerified by operator
Filing propagation · 10 filings · 10 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last May 17 (HI) — a 136-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.