Central Oregon Community College
ent_a56f0d9e2e467d594874e3fa
Disclosures
5
State AG · 5 jurisdictions
Incidents
2
filings grouped by incident
Max affected reported
5,210
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Central Oregon Community College
- Normalized
- central oregon community college— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- cocc.edu
Disclosure history (5)newest first
- 🦞Maine State AGas victim2025-03-05
Central Oregon Community College reported a data breach affecting 4 Maine residents. The breach was discovered on February 24, 2025, and occurred on December 21, 2024. The college is offering 12 months of credit monitoring and identity protection services through IDX by Zerofox to those affected.
- 🏎️Indiana State AGas victim2025-02-28
Central Oregon Community College reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-21 and was reported on 2025-02-28. 2 Indiana residents were affected. 5,210 individuals affected in total.
- 🦬Montana State AGas victim2025-02-28
Central Oregon Community College reported a data breach to the Montana Attorney General. The breach was reported on 2025-02-28. The breach occurred on 12/21/2024. 19 Montana residents were affected.
- 🍁Vermont State AGas reporting2025-02-28
Central Oregon Community College (COCC) notified the Vermont AG that its third-party administrator, Carruth Compliance Consulting, experienced a data security incident on December 21, 2024. The breach potentially exposed employees' names, SSNs, financial account info, driver's licenses, W-2s, and medical billing data. COCC is offering 12 months of credit monitoring and identity theft protection via IDX to affected individuals.
- 🦫Oregon State AGas victim2025-02-28
Central Oregon Community College reported a data breach to the Oregon Attorney General. The breach was reported on 2025-02-28. The breach occurred during 12/19/2024 - 12/16/2024. The breach was discovered on 2/24/2025. 5,210 individuals were affected. Notice was sent on 2/28/2025.