Comparison Overview
UT Southwestern Medical Center
UT Southwestern Medical Center
5323 Harry Hines Boulevard, Dallas, Texas, US, 75390
Last Update: 04/04/2026
UT Southwestern is an academic medical center, world-renowned for its research, regarded among the best in the country for medical education and for clinical and scientific training, and nationally recognized for the quality of care its faculty provides to patients at U...
Mayo Clinic
200 First St. S.W., Rochester, 55905, US
Last Update: 08/06/2026
Mayo Clinic has expanded and changed in many ways, but our values remain true to the vision of our founders. Our primary value – The needs of the patient come first – guides our plans and decisions as we create the future of health care. Join us and you'll find a cultur...
Compliance Ranges Comparison
UT Southwestern Medical Center
Mayo Clinic
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UT Southwestern Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Mayo Clinic has 92.31% more incidents than the average of all companies with at least one recorded incident.
Incident History - UT Southwestern Medical Center (X = Date, Y = Severity)
UT Southwestern Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mayo Clinic (X = Date, Y = Severity)
Mayo Clinic cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UT Southwestern Medical Center
Mayo Clinic
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.