Comparison Overview
PopHealthCare
PopHealthCare
113 Seaboard Lane, Franklin, Tennessee, 37067, US
Last Update: 28/03/2026
At PopHealthCare, we believe healthcare should be personal. For us, that means bringing care to those who need it most, where they will be able to achieve their health goals best–at home or wherever they reside. Using in-home assessments and cutting-edge analytics, we...
Health Care Service Corporation
300 E Randolph St, Chicago, 60601, US
Last Update: 02/04/2026
Health Care Service Corporation serves nearly 23 million people across the United States through its portfolio of health benefit solutions. HCSC provides health coverage options for employers large and small, individuals and families, and Medicare and Medicaid plans. H...
Compliance Ranges Comparison
PopHealthCare
Health Care Service Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for PopHealthCare in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Health Care Service Corporation in 2026.
Incident History - PopHealthCare (X = Date, Y = Severity)
PopHealthCare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Health Care Service Corporation (X = Date, Y = Severity)
Health Care Service Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PopHealthCare
Health Care Service Corporation
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.