SSL and ACL
ent_ea6004b875743d09f3dd6808
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
57,253
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- SSL and ACL
- Normalized
- ssl and acl— 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 (4)newest first
- ⭐Texas State AGas victim2026-01-05
SSL and ACL and their current and former affiliates based in Salt Lake City, Utah, a insurance services entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-12-17 and reported on 2026-01-05. 4,919 Texas residents were affected. 57,253 individuals affected in total. Types of information involved: Social Security Number Information;Driver’s License number;Financial Information (e.g. account number, credit or debit card number);Medical Information;Health Insurance Information. Consumers were notified via U.S. Mail.
- 🦞Maine State AGas victim2025-12-30
SSL and ACL and their current and former affiliates reported a data breach affecting 57,253 individuals, including 24 Maine residents. The breach, which occurred on April 7, 2025, was discovered on December 17, 2025. The company notified affected individuals on December 30, 2025, and is offering 12 months of credit monitoring and identity restoration services through IDX. The breach was the result of an external system breach (hacking).
- 🏎️Indiana State AGas victim2025-12-30
SSL and ACL and their current and former affiliates reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-07 and was reported on 2025-12-30. 1,205 Indiana residents were affected. 57,253 individuals affected in total.
- 🦫Oregon State AGas victim2025-12-30
SSL and ACL and their current and former affiliates reported a data breach to the Oregon Attorney General. The breach was reported on 2025-12-30. The breach occurred during 1/1/0001, 4/7/2025 - 4/15/2025. The breach was discovered on 4/15/2025. 57,253 individuals were affected. Notice was sent on 12/30/2025.