Comparison Overview
Resecurity
Resecurity
445 S Figueroa St, Los Angeles, 90071, US
Last Update: 08/06/2026
Resecurity is an American company with headquarters in Los Angeles, California. The company provides next-generation ISR (Intelligence, Surveillance, Reconnaissance) and ERMM (External Risk Mitigation & Management) solutions to leading Fortune 500 corporations, law enfo...
Amentum
4800 Westfields Blvd, 400, Chantilly, Virginia, US, 20151
Last Update: 28/03/2026
Amentum is a global leader in advanced engineering and innovative technology solutions, trusted by the United States and its allies to address their most significant and complex challenges in science, security and sustainability. Our people apply undaunted curiosity, re...
Compliance Ranges Comparison
Resecurity
Amentum
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Resecurity has 9.09% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Amentum in 2026.
Incident History - Resecurity (X = Date, Y = Severity)
Resecurity cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amentum (X = Date, Y = Severity)
Amentum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Resecurity
Amentum
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: *.*.