City of Jacksonville Beach, Florida
ent_704359121a611aef60c8ec8c
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
48,949
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- City of Jacksonville Beach, Florida
- Normalized
- city of jacksonville beach florida— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- 🏎️Indiana State AGas victim2024-03-20
City of Jacksonville Beach Forida reported a data breach to the Indiana Attorney General. The breach occurred on 2024-01-22 and was reported on 2024-03-20. 83 Indiana residents were affected. 48,949 individuals affected in total.
- 🦬Montana State AGas victim2024-03-20
City of Jacksonville Beach, Florida reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-20. The breach occurred from 1/22/2024 to 1/29/2024. 15 Montana residents were affected.
- 🦞Maine State AGas victim2024-03-20
The City of Jacksonville Beach, Florida, experienced a data breach impacting 38 Maine residents. The breach, which occurred between January 22 and January 29, 2024, was discovered on February 22, 2024. The incident was a result of an external system breach (hacking), leading to the compromise of names and Social Security numbers. Affected individuals were notified on March 20, 2024, and offered 12 months of identity restoration and credit monitoring services through Epiq.
- ⛰️New Hampshire State AGas victim2024-03-20
City of Jacksonville Beach, FL notified 36 New Hampshire residents of a cybersecurity event occurring between Jan 22-29, 2024. Unauthorized access to systems resulted in data exfiltration. COJB engaged law enforcement, implemented safeguards, and offered credit monitoring via Equifax.
- 🍁Vermont State AGas victim2024-03-13
The City of Jacksonville Beach, FL, notified consumers of a cybersecurity event occurring between January 22 and January 29, 2024. Unauthorized access to certain files resulted in the potential exposure of names and government identifiers (e.g., SSN). The City engaged forensic investigators, enhanced security measures, and offered credit monitoring services. The investigation is ongoing.