norm: regence regence bs regence bsi and regence bcbsono LEI · no CIKMax severity: Low

Canonical registry

Regence (Regence BS, Regence BSI and Regence BCBSO)

ent_dbaabf11b7e1243b1149f9af

Compliance scorecard →🔔 Follow entity

Disclosures

1

State AG · 1 jurisdiction

Incidents

—

no linked incident in sample

Max affected reported

706

as filed · State AG WA

Leak-site claims

0

none in sample

Identity resolution

Canonical name: Regence (Regence BS, Regence BSI and Regence BCBSO)
Normalized: regence regence bs regence bsi and regence bcbso— 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 (1)newest first

🌲Washington State AGas victim2025-05-06
Regence (Regence BS, Regence BSI and Regence BCBSO), a health sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2024-11-21 and filed notice on 2025-05-06. 706 Washington residents were affected. 166 days elapsed between awareness and notification. 16 days to identify the breach. 0 days to contain the breach.