Comparison Overview
Firetrace International, a Halma Company
Firetrace International, a Halma Company
8435 N. 90th St, Scottsdale, AZ, 85258, US
Last Update: 30/01/2026
Firetrace International, a Halma company, is a global innovator and manufacturer of industry leading fire suppression systems; both pre-engineered for special hazard enclosures and engineered clean agent systems for larger enclosures, as well as full room total flooding...
Prosegur
Pajaritos, 24, Madrid, 28007, ES
Last Update: 02/04/2026
At Prosegur, being aware of who we are is what defines our identity and commitment. 🌐 We are Prosegur. Leaders in the private security sector for more than 45 years and in more than 30 countries. 💡 We are innovation. We reinvent ourselves, adapt and integrate trends t...
Compliance Ranges Comparison
Firetrace International, a Halma Company
Prosegur
Benchmark & Cyber Underwriting Signals
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Firetrace International, a Halma Company in 2026.
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Prosegur in 2026.
Incident History - Firetrace International, a Halma Company (X = Date, Y = Severity)
Firetrace International, a Halma Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Prosegur (X = Date, Y = Severity)
Prosegur cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Firetrace International, a Halma Company
Prosegur
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: *.*.