Long Beach
ent_5cde3c3ea1e1193a916d5404
Disclosures
5
State AG · HHS OCR · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
470,060
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Long Beach
- Normalized
- long beach— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- cityoflongbeach.org
Disclosure history (5)newest first
- 🦬Montana State AGas victim2025-04-14
The City of Long Beach, CA reported a data breach to the Montana Attorney General. The breach was reported on 2025-04-14. The breach occurred on 11/14/2023. 109 Montana residents were affected.
- 🦫Oregon State AGas victim2025-04-14
The City of Long Beach, CA reported a data breach to the Oregon Attorney General. The breach was reported on 2025-04-14. The breach occurred during 11/14/2023. The breach was discovered on 3/18/2025. 470,060 individuals were affected. Notice was sent on 4/14/2025.
- CALIFORNIAHHS OCRas victim2025-04-14
The City of Long Beach, CA reported to HHS on 2025-04-14 a Hacking/IT Incident affecting 258,191 individuals. Breached information located on Network Server.
- 🐻California State AGas victim2025-04-14
On or about November 14, 2023, the City of Long Beach, CA experienced a cybersecurity incident in which an unauthorized actor obtained access to the City's network. After an extensive forensic investigation and manual document review, the City determined on March 18, 2025 that certain impacted files containing personal information (including SSNs) may have been accessed and/or acquired. Affected individuals were notified via letter dated April 14, 2025, and offered complimentary Experian IdentityWorks credit monitoring.
- 🌲Washington State AGas victim2025-04-14
The City of Long Beach CA, a government sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-11-14 and filed notice on 2025-04-14. 983 Washington residents were affected. 517 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.