Enroll Confidently
ent_52fc5303197f40803355f279
Disclosures
5
State AG · 5 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
57,763
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Enroll Confidently
- Normalized
- enroll confidently— 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
- 🦬Montana State AGas victim2024-08-16
Enroll Confidently reported a data breach to the Montana Attorney General. The breach was reported on 2024-08-16. The breach occurred on 2/13/2024. 101 Montana residents were affected.
- 🏎️Indiana State AGas victim2024-08-16
Enroll Confidently Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-13 and was reported on 2024-08-16. 459 Indiana residents were affected. 57,763 individuals affected in total.
- ⛰️New Hampshire State AGas victim2024-08-16
Enroll Confidently, Inc. notified New Hampshire AG of a data breach discovered on Feb 13, 2024. An unauthorized actor accessed the network and copied files containing PII (names, addresses, SSNs). The company secured systems, notified federal law enforcement, and offered credit monitoring. Approximately 597 Rhode Island residents were impacted.
- 🐻California State AGas victim2024-08-16
Enroll Confidently, Inc. reported that on February 13, 2024, an unauthorized actor gained access to its network and copied certain files containing personal information, including names. The company secured its systems, notified federal law enforcement, and is offering 24 months of credit monitoring to affected individuals. The incident involved customer data from employers and benefits providers using the platform.
- 🌲Washington State AGas victim2024-08-16
Enroll Confidently, Inc, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-02-13 and filed notice on 2024-08-16. 694 Washington residents were affected. 185 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.