A10 NETWORKS, INC.
bd_a8ec6a516475477b · schema v1 · pii pii-v2
Full breach record for A10 NETWORKS, INC. →2 incidents on fileA10 Networks, Inc. filed an 8-K on February 7, 2023 disclosing, under Item 8.01, that on January 23, 2023 it identified a cyber-security incident in its corporate IT infrastructure, which it said was not related to any of its products or solutions used by its customers. The company launched an investigation, engaged cyber-security experts and advisors, incident response professionals and external counsel, contained the attack within its network, and notified the appropriate law enforcement authorities. It currently does not expect the incident to have a material impact on its operations. The filing does not state what data, if any, was involved or how many people were affected.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Feb 7, 2023
Filed
No interval is drawn: no breach start or discovery date is on record for this filing.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteplaybd_fe621f8d0d8849ca2023-02-09 · +2dVerified by operator
Regulatory filings (2) · sorted by filing gap
- Indiana State AGbd_25d93d6dff6decbc2023-02-10 · +3dVerified by operator
- Massachusetts State AGbd_974e13f28e81eeb22023-03-02 · +23dVerified by operator
Filing propagation · 3 filings · 2 states
View merged incident ↗Pattern: first filing Feb 7, last Mar 2 (MA) — a 23-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.