Form I-9 Compliance
bd_10613a0a365ff047 · 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 on or about February 5, 2024. The company became aware of the activity on April 12, 2024. Affected data included names and addresses. The company engaged external experts, reported to law enforcement, reset credentials, and offered credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 5, 2024
Begins
Apr 12, 2024
Discovered
Oct 17, 2024
Filed
vs. sector median
+8 wks slower
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Oregon State AGbd_1338e71db161428e2024-10-16 · +1dVerified
- Washington State AGbd_511b3bdd2f8e61d92024-10-16 · +1dVerified
- New Hampshire State AGbd_a28159e439c286e82024-10-15 · +2dVerified
- Vermont State AGbd_047033e7a754f0822024-10-12 · +5dVerified
Show 3 more filings ↓Show fewer ↑up to 21d gap
- Maine State AGbd_28932f4137a33d4f2024-10-11 · +6dCandidate
- California State AGbd_b80f1ea48e5293082024-10-11 · +6dVerified
- Maine State AGbd_600a2c44a7e82cf62024-11-07 · +21dVerified
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.