Comparison Overview
Epworth

Epworth
89 Bridge Rd, Richmond, Victoria, AU, 3121
Last Update: 13/03/2026
As Victoria's largest not-for-profit private hospital group, Epworth HealthCare offers leading solutions in diagnosis, clinical treatment, and rehabilitation. From maternity services to cancer treatment programs, our team offers exceptional patient care 24 hours a day, ...

Sharp HealthCare
8695 Spectrum Center Blvd., San Diego, 92123, US
Last Update: 30/03/2026
Sharp HealthCare is a not-for-profit health care system based in San Diego, California, with four acute care hospitals, three specialty hospitals, three medical groups and a health plan. We provide medical services in virtually all fields of medicine, including primary ...
Compliance Ranges Comparison

Epworth







Sharp HealthCare






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Epworth has 29.08% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Sharp HealthCare in 2026.
Incident History - Epworth (X = Date, Y = Severity)
Epworth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sharp HealthCare (X = Date, Y = Severity)
Sharp HealthCare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Epworth

Sharp HealthCare
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.