Comparison Overview
Regence BlueCross BlueShield of Oregon
Regence BlueCross BlueShield of Oregon
100 SW Market St, Portland, 97201, US
Last Update: 03/04/2026
Regence is part of a family of regional health plans that have been a symbol of strength and stability in local communities for more than 100 years. We connect people and their families to health care when and where they need it most. Powered by the national strength a...
Intact
700 University Avenue, Toronto, M5G 0A1, CA
Last Update: 01/04/2026
We created a purpose-driven company based on Values and a belief that insurance is about people, not things. This is the foundation on which we have built Intact and it lives every day through our purpose, Values, what we aim to achieve and how. ___ Nous sommes là pour...
Compliance Ranges Comparison
Regence BlueCross BlueShield of Oregon
Intact
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Regence BlueCross BlueShield of Oregon in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Intact in 2026.
Incident History - Regence BlueCross BlueShield of Oregon (X = Date, Y = Severity)
Regence BlueCross BlueShield of Oregon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intact (X = Date, Y = Severity)
Intact cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Regence BlueCross BlueShield of Oregon
Intact
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.