Comparison Overview
Mount Sinai St. Luke's

Mount Sinai St. Luke's
1111 Amsterdam Avenue, New York, 10025, US
Last Update: 20/02/2026
With 523 beds, St. Luke’s serves as the principal health care provider for the West Harlem and Morningside Heights communities and operates one of Manhattan’s few Level 1 trauma services. Founded in 1847, it is home to the Al-Sabah Arrhythmia Institute, a world-class, m...

Ardent Health
340 Seven Springs Way, Suite 100, Nashville, Tennessee, US, 37027
Last Update: 02/04/2026
Ardent Health is a leading provider of healthcare in growing mid-sized urban communities across the U.S. With a focus on people and investments in innovative services and technologies, Ardent is passionate about making healthcare better and easier to access. Through its...
Compliance Ranges Comparison

Mount Sinai St. Luke's







Ardent Health






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Mount Sinai St. Luke's in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Ardent Health in 2026.
Incident History - Mount Sinai St. Luke's (X = Date, Y = Severity)
Mount Sinai St. Luke's cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ardent Health (X = Date, Y = Severity)
Ardent Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mount Sinai St. Luke's

Ardent Health
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.