Comparison Overview
Providence Alaska
Providence Alaska
3200 Providence Dr, Anchorage, 99508, US
Last Update: 09/03/2026
Providence first brought health care to Nome, Alaska, in 1902. Today we are the state’s largest private employer, providing care in Anchorage, Eagle River, Kodiak Island, Mat-Su, Seward, and Valdez. Visit providence-alaska.jobs to view our job openings.
Hospital Authority
Hospital Authority Building, Hong Kong, 852, HK
Last Update: 04/04/2026
The Hospital Authority (HA) is a statutory body established under the Hospital Authority Ordinance in 1990. We have been responsible for managing Hong Kong's public hospitals services since December 1991. We are accountable to the Hong Kong Special Administrative Region...
Compliance Ranges Comparison
Providence Alaska
Hospital Authority
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Providence Alaska in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Hospital Authority has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Providence Alaska (X = Date, Y = Severity)
Providence Alaska cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hospital Authority (X = Date, Y = Severity)
Hospital Authority cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Providence Alaska
Hospital Authority
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.