Comparison Overview
Johns Hopkins Biomedical Engineering
Johns Hopkins Biomedical Engineering
undefined, Baltimore, MD, 21218, US
Last Update: 05/12/2025
Established in 1961, the Johns Hopkins Department of Biomedical Engineering (BME) is home to the nation’s first training program in the field. Consistently ranked the #1 BME department in the country, our mission is to advance human health by training biomedical enginee...
The Ohio State University
190 N Oval Mall, Columbus, Ohio, US, 43210
Last Update: 01/04/2026
One of the largest universities in the United States, The Ohio State University is a leading research university and the model for Ohio's public higher education institutes. Founded in 1870 as a land-grant university, it consistently ranks as one of the top public unive...
Compliance Ranges Comparison
Johns Hopkins Biomedical Engineering
The Ohio State University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Johns Hopkins Biomedical Engineering in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for The Ohio State University in 2026.
Incident History - Johns Hopkins Biomedical Engineering (X = Date, Y = Severity)
Johns Hopkins Biomedical Engineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Ohio State University (X = Date, Y = Severity)
The Ohio State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Johns Hopkins Biomedical Engineering
The Ohio State University
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.