Comparison Overview
Johns Hopkins Systems Engineering for Professionals

Johns Hopkins Systems Engineering for Professionals
3400 North Charles Street, Baltimore, Maryland, 21218, US
Last Update: 27/02/2026
This systems-centric program keeps engineers and scientists engaged in and on the leading edge of all aspects of analysis, design, integration, production, and operation of modern systems. Learn from instructors who are leading practitioners in the field of systems engi...

Brown University
One Prospect Street, Providence, Rhode Island, US, 02912
Last Update: 30/07/2026
Located in historic Providence, Rhode Island and founded in 1764, Brown University is the seventh-oldest college in the United States. Brown is an independent, coeducational Ivy League institution comprising undergraduate and graduate programs, plus the Alpert Medical S...
Compliance Ranges Comparison

Johns Hopkins Systems Engineering for Professionals







Brown University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Johns Hopkins Systems Engineering for Professionals in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Brown University in 2026.
Incident History - Johns Hopkins Systems Engineering for Professionals (X = Date, Y = Severity)
Johns Hopkins Systems Engineering for Professionals cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Brown University (X = Date, Y = Severity)
Brown University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Johns Hopkins Systems Engineering for Professionals

Brown University
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)