Comparison Overview
McLaren Lapeer Region
McLaren Lapeer Region
1375 N Main St, Lapeer, Michigan, 48446, US
Last Update: 31/03/2026
To apply to available positions at McLaren Lapeer Region, please visit www.mclaren.org/careers. McLaren Lapeer Region is a 222-bed acute care facility located in Lapeer, Michigan, and is the primary provider of health care services to Lapeer County and the surrounding...
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
McLaren Lapeer Region
Mayo Clinic
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for McLaren Lapeer Region 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 - McLaren Lapeer Region (X = Date, Y = Severity)
McLaren Lapeer Region 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
McLaren Lapeer Region
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.