Sarku Japan
bd_3e7e01e462f64ab0 · schema v1 · pii pii-v1
Full breach record for Sarku Japan →5 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
2 wks faster
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Washington State AGbd_154978068a8580a42022-03-16Candidate
- Maine State AGbd_676946af941027ba2022-03-16Verified
- Oregon State AGbd_6f1f4c9b26bfab192022-03-16Verified
- California State AGbd_2e9e3b153a51c8a62022-08-08 · +145dVerified
Show 1 more filing ↓Show fewer ↑up to 145d gap
- Maine State AGbd_e82af6a75bb3e3f12022-08-08 · +145dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Mar 16 (WA), last Aug 8 (ME) — a 145-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.