Oklahoma Department of Securities
bd_f49fe78928e1c8de · schema v1 · pii pii-v1
Full breach record for Oklahoma Department of Securities →The Oklahoma Department of Securities experienced a cybersecurity incident involving unauthorized access to its network. The attacker used valid credentials to access systems, exfiltrate data, and potentially encrypt files. The department engaged forensic investigators, notified law enforcement, and provided credit monitoring to affected individuals. The incident is currently contained.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 20, 2019
Filed
No interval is drawn: no breach start or discovery date is on record for this filing.
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- California State AGbd_aa9b3bc3bf25cb022019-06-20Verified
- Hawaii State AGbd_f7e37dafbbc657922019-06-25 · +5dVerified
- South Carolina State AGbd_49e4f489a4804ba82019-05-17 · +34dVerified
- Montana State AGbd_be9f601eefc620a92019-05-15 · +36dVerified
Show 5 more filings ↓Show fewer ↑up to 41d gap
- New Hampshire State AGbd_803890bd7782bce82019-05-14 · +37dVerified
- Oregon State AGbd_29d6b355db753a9d2019-05-10 · +41dCandidate
- California State AGbd_897572ad763d92b62019-05-10 · +41dVerified
- Massachusetts State AGbd_a232e39f84e19ea52019-05-10 · +41dVerified
- Washington State AGbd_ec24a2e2a284b1032019-05-10 · +41dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing May 10 (OR), last Jun 25 (HI) — a 46-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.