Comparison Overview
UW-Madison College of Engineering
UW-Madison College of Engineering
1415 Engineering Dr, Madison, Wisconsin, US, 53706
Last Update: 01/03/2026
We are a thriving, top-ranked college in Madison, Wisconsin—one of the most fantastic cities in the country. We think boldly and act confidently not only as engineers, but as engaged citizens. As an engineering community, we value unique perspectives, we foster respect ...
Louisiana State University
Louisiana State University, Baton Rouge, la, US, 70803
Last Update: 02/04/2026
LSU is the flagship institution of Louisiana and is one of only 30 universities nationwide holding land-grant, sea-grant and space-grant status. Since 1860, LSU has served its region, the nation, and the world through extensive, multipurpose programs encompassing ins...
Compliance Ranges Comparison
UW-Madison College of Engineering
Louisiana State University
Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for UW-Madison College of Engineering in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Louisiana State University in 2026.
Incident History - UW-Madison College of Engineering (X = Date, Y = Severity)
UW-Madison College of Engineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Louisiana State University (X = Date, Y = Severity)
Louisiana State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UW-Madison College of Engineering
Louisiana 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.