Comparison Overview
Philippine Statistics Authority
Philippine Statistics Authority
PSA Complex, East Avenue, Diliman, Quezon City, 1101, PH
Last Update: 09/07/2026
The PSA is the central statistical authority of the Philippine government that collects, compiles, analyzes and publishes statistical information on economic, social, demographic, political affairs and general affairs of the people of the Philippines and enforces the ci...
State of Florida
US
Last Update: 03/04/2026
Join Florida’s talented workforce to fulfill your professional goals and achieve a meaningful career. Our talented public servants work hard to serve more than 19 million residents across Florida, and you, too, can realize success in the Sunshine State. Working in F...
Compliance Ranges Comparison
Philippine Statistics Authority
State of Florida
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
Philippine Statistics Authority 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 State of Florida in 2026.
Incident History - Philippine Statistics Authority (X = Date, Y = Severity)
Philippine Statistics Authority cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Florida (X = Date, Y = Severity)
State of Florida cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Philippine Statistics Authority
State of Florida
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: *.*.