MidFirst Bank
bd_e933a0e5fa8c3b69 · schema v1 · pii pii-v1
Full breach record for MidFirst Bank →2 incidents on fileCalifornia AG SB24 submission for MidFirst Bank regarding a data breach. The notification letter is a sample template offering 24-month OnAlert identity monitoring and credit bureau guidance. Specific breach details, dates, and affected individual counts are not present in the provided source text.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Aug 21, 2023
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- Montana State AGbd_3f83236ccf1420dd2023-08-21Verified
- Massachusetts State AGbd_5eec0209f5842ab82023-08-21Verified
- Oregon State AGbd_63b23748175961ff2023-08-21Verified
- Washington State AGbd_4cdab9b39b8d07192023-08-04 · +17dCandidate
Filing propagation · 5 filings · 5 states
View merged incident ↗Pattern: first filing Aug 4 (WA), last Aug 21 (CA) — a 17-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.