Cardinal Logistics Management Corp.
bd_ce279121db2d821e · schema v1 · pii pii-v1
Full breach record for Cardinal Logistics Management Corp. →Cardinal Logistics Management Corp. experienced a ransomware attack on October 20, 2020, resulting in the encryption of several systems. The incident potentially exposed personal information of current and former employees, including names and other data elements. The company launched an investigation, contained the incident, and offered credit monitoring services to affected individuals. No actual misuse of data was confirmed.
J jump to incidentP pin to compareR raw source
Incident timeline
Oct 20, 2020
Begins
Oct 20, 2020
Discovered
Mar 2, 2021
Filed
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Oregon State AGbd_1a17d74a4d4210a72021-03-02Candidate
- Indiana State AGbd_256228e537ccbe2e2021-03-02Verified
- Massachusetts State AGbd_31a3ca05d6de9db22021-03-02Verified
- Montana State AGbd_bce9b51fb24a01892021-03-02Verified
Show 4 more filings ↓Show fewer ↑up to 60d gap
- Maine State AGbd_e6772ee799add6c62021-03-02Verified
- Washington State AGbd_e74aee4c1a224dd22021-03-02Verified
- New Hampshire State AGbd_6a07fdb27af03c112021-03-15 · +13dVerified
- Illinois State AGbd_f9403584bede34842021-01-01 · +60dVerified
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Mar 15 (NH) — a 73-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.