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 ...

Arizona State University
1151 S Forest Ave, Tempe, AZ, US, 85281
Last Update: 18/08/2026
ASU has developed a new model for the American research university, creating an institution committed to excellence, access and impact — the New American University. Nationally and internationally acclaimed, ASU ranks among the very best in nearly every critical measu...
Compliance Ranges Comparison

UW-Madison College of Engineering







Arizona 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)
Arizona State University has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
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 - Arizona State University (X = Date, Y = Severity)
Arizona State University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UW-Madison College of Engineering

Arizona State University
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.