Sarku Japan
bd_3e7e01e462f64ab0 · schema v1 · pii pii-v1
Full breach record for Sarku Japan →3 incidents on fileSarku Japan disclosed that an unauthorized actor gained access to certain systems between January 13 and February 6, 2022. The company discovered the incident on February 6, 2022. Affected data may include names, addresses, dates of birth, and Social Security numbers. The company offered 12 months of identity monitoring through Kroll.
J jump to incidentP pin to compareR raw source
Incident timeline
Jan 13, 2022
Begins
Feb 6, 2022
Discovered
Mar 16, 2022
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Washington State AGbd_154978068a8580a42022-03-16Candidate
- Indiana State AGbd_3aca2a3d12cc197b2022-03-16Verified by operator
- Massachusetts State AGbd_4842d37d019f458e2022-03-16Verified by operator
- Maine State AGbd_676946af941027ba2022-03-16Verified
Show 5 more filings ↓Show fewer ↑up to 149d gap
- Oregon State AGbd_6f1f4c9b26bfab192022-03-16Verified
- New Hampshire State AGbd_82f05d9f8f47e5332022-03-21 · +5dVerified by operator
- California State AGbd_2e9e3b153a51c8a62022-08-08 · +145dVerified
- Maine State AGbd_e82af6a75bb3e3f12022-08-08 · +145dVerified
- New Hampshire State AGbd_c728b2a05ad2d3562022-08-12 · +149dVerified by operator
Filing propagation · 10 filings · 7 states
View merged incident ↗Pattern: first filing Mar 16 (WA), last Aug 12 (NH) — a 149-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.