Form I-9 Compliance
bd_047033e7a754f082 · schema v1 · pii pii-v1
Full breach record for Form I-9 Compliance →4 incidents on fileForm I-9 Compliance reported a cybersecurity incident where an unauthorized third party accessed its network between Feb 5 and Apr 12, 2024. The breach affected customer personal information including name, address, and other data elements. Form I-9 engaged external experts, reset credentials, and offered 24 months of credit monitoring. No fraud was detected at the time of filing.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 5, 2024
Begins
Apr 12, 2024
Discovered
Oct 12, 2024
Filed
vs. sector median
+7 wks slower
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Maine State AGbd_28932f4137a33d4f2024-10-11 · +1dCandidate
- California State AGbd_b80f1ea48e5293082024-10-11 · +1dVerified
- New Hampshire State AGbd_a28159e439c286e82024-10-15 · +3dVerified
- Oregon State AGbd_1338e71db161428e2024-10-16 · +4dVerified
Show 3 more filings ↓Show fewer ↑up to 26d gap
- Washington State AGbd_511b3bdd2f8e61d92024-10-16 · +4dVerified
- South Carolina State AGbd_10613a0a365ff0472024-10-17 · +5dVerified
- Maine State AGbd_600a2c44a7e82cf62024-11-07 · +26dVerified
Filing propagation · 8 filings · 7 states
View merged incident ↗Pattern: first filing Oct 11 (ME), last Nov 7 (ME) — a 27-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.