1st Source Bank
bd_ee5f8afdf477969e · schema v1 · pii pii-v1
Full breach record for 1st Source Bank →6 incidents on file1st Source Bank reported a ransomware incident that was discovered on June 1, 2023. The breach impacted approximately 450,000 individuals, compromising their names and Social Security numbers. The bank began notifying affected parties on July 14, 2023, and offered 12 months of identity monitoring services through Kroll.
J jump to incidentP pin to compareR raw source
Incident timeline
Jun 1, 2023
Begins
Jun 1, 2023
Discovered
Jul 19, 2023
Filed
vs. sector median
3 wks faster
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- California State AGbd_504a71c703e7184f2023-07-19Verified
- Montana State AGbd_644846888cf47c7f2023-07-19Verified
- Washington State AGbd_d0cebba25691bccf2023-07-20 · +1dVerified
- Oregon State AGbd_db8e5883d0d70d122023-07-20 · +1dVerified
Show 5 more filings ↓Show fewer ↑up to 9d gap
- Vermont State AGbd_a872f10fb82b1c592023-07-14 · +5dCandidate
- California State AGbd_4a59c8811709f62b2023-07-26 · +7dVerified
- New Hampshire State AGbd_fda2be588d0437762023-07-26 · +7dVerified
- Oregon State AGbd_08c27ccfede4e9ef2023-07-27 · +8dVerified
- SEC 8-Kbd_66ec9f2d6644e6032023-07-10 · +9dVerified
Filing propagation · 10 filings · 7 states
View merged incident ↗Pattern: first filing Jul 10, last Jul 27 (OR) — 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.