Comparison Overview
Borgess Health
Borgess Health
1521 Gull Road, Kalamazoo, Michigan, 49048, US
Last Update: 30/01/2026
Based in Kalamazoo, we provide care for nearly 1 million people annually in cardiac, neurologic, orthopedic, vascular and bariatric services, among others. We are one of the region’s largest health systems and employers and have been serving as part of Ascension, the na...
Johnson & Johnson
New Brunswick, NJ, US, 08903
Last Update: 28/06/2026
At Johnson & Johnson, we believe health is everything. Our strength in healthcare innovation empowers us to build a world where complex diseases are prevented, treated, and cured, where treatments are smarter and less invasive, and solutions are personal. Through our ex...
Compliance Ranges Comparison
Borgess Health
Johnson & Johnson
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Borgess Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Johnson & Johnson has 92.31% more incidents than the average of all companies with at least one recorded incident.
Incident History - Borgess Health (X = Date, Y = Severity)
Borgess Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson & Johnson (X = Date, Y = Severity)
Johnson & Johnson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Borgess Health
Johnson & Johnson
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.