Comparison Overview
Alabama Department of Public Health
Alabama Department of Public Health
201 Monroe Street, Montgomery, 36104, US
Last Update: 23/06/2026
The Alabama Department of Public Health (ADPH) is the state's primary health agency. With approximately 2,700 employees, ADPH is one of the largest state agencies. ADPH aims to provide public health "services for the improvement and protection of the public’s health thr...
City of Seattle
Seattle City Hall, Seattle, 98124, US
Last Update: 01/04/2026
Work With Purpose. Shape Seattle. Inspire the World. Seattle is more than a world-class city — it’s a vibrant, evolving community rooted in shared values of sustainability, innovation, and inclusion. As a public employer, the City of Seattle is committed to building a ...
Compliance Ranges Comparison
Alabama Department of Public Health
City of Seattle
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
Alabama Department of Public Health has 30.56% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Seattle in 2026.
Incident History - Alabama Department of Public Health (X = Date, Y = Severity)
Alabama Department of Public Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - City of Seattle (X = Date, Y = Severity)
City of Seattle cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Alabama Department of Public Health
City of Seattle
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.