Canon U.S.A., Inc.
bd_4175ed66eb6f67f4 · schema v1 · pii pii-v1
Full breach record for Canon U.S.A., Inc. →2 incidents on fileCanon U.S.A., Inc. disclosed a ransomware incident identified on August 4, 2020, involving unauthorized access to file servers between July 20 and August 6, 2020. The breach affected current and former employees (2005-2020) and their beneficiaries, exposing names, SSNs, driver's licenses, financial account numbers, and dates of birth. Canon engaged forensic investigators, notified law enforcement, and offered credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 20, 2020
Begins
Aug 4, 2020
Discovered
Nov 25, 2020
Filed
vs. sector median
3 wks faster
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Massachusetts State AGbd_52279bcc6e3c0f3e2020-11-25Verified
- Oregon State AGbd_56edf754b5e772342020-11-25Verified
- Indiana State AGbd_b2296d0bec2e160b2020-11-25Verified
- Maine State AGbd_c755f04850c8e8362020-11-25Verified
Show 2 more filings ↓Show fewer ↑up to 5d gap
- California State AGbd_cd9c7ef755d53ecb2020-11-25Verified
- New Hampshire State AGbd_19d9735790b475812020-11-30 · +5dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Nov 25 (MA), last Nov 30 (NH) — a 5-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.