Colorado Bankers Life Insurance Company
ent_019e5a1d004e48d10aad461dd888ffa3
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
99,797
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Colorado Bankers Life Insurance Company
- Normalized
- colorado bankers life insurance— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 549300DLB7VUWD515L33
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- 🦬Montana State AGas victim2018-08-03
Colorado Bankers Life Insurance Company reported a data breach to the Montana Attorney General. The breach was reported on 2018-08-03. The breach occurred from 3/28/2018 to 4/13/2018. 129 Montana residents were affected.
- 🦫Oregon State AGas victim2018-08-03
Colorado Bankers Life Insurance Company reported a data breach to the Oregon Attorney General. The breach was reported on 2018-08-03. The breach occurred during 3/28/2018 - 3/28/2018. The breach was discovered on 6/14/20186/20/2018. 99,797 individuals were affected. Notice was sent on 8/3/2018.
- 🐻California State AGas victim2018-08-03
Colorado Bankers Life Insurance Company reported a targeted phishing incident affecting employee cloud-based email accounts between March 28 and April 13, 2018. The attack compromised employee credentials, leading to the exposure of policyholder and producer personal information (names, addresses, SSNs). CBLLife secured accounts, engaged forensic investigators, and provided one year of complimentary credit monitoring to affected individuals. The internal network was not affected.
- 🌲Washington State AGas victim2018-08-03
Colorado Bankers Life Insurance Company, a finance sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2018-06-14 and filed notice on 2018-08-03. 956 Washington residents were affected. 50 days elapsed between awareness and notification. 78 days to identify the breach. 0 days to contain the breach.