Comparison Overview
Ageological
Ageological
Avenida La Cantera, Coquimbo, coquinbo, undefined, CL
Last Update: 27/02/2026
Analytical Geological Services, parte del Grupo Cotecna, es un laboratorio de ensayos, ubicado en la comuna de Coquimbo, IV región. Chile, que presta servicios de análisis ambientales y mineros, utilizando métodos normalizados y propios según sea los requerimientos de n...
BHP
171 Collins Street, Melbourne, 3000, AU
Last Update: 07/07/2026
We are supplying the resources the world needs to help build a better, clearer future. Copper for renewable energy. Potash for sustainable farming. Iron ore and metallurgical coal for the steel needed for global infrastructure and the energy transition. #FutureIsClear ...
Compliance Ranges Comparison
Ageological
BHP
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Ageological in 2026.
Incidents vs Mining Industry Avg (This Year)
BHP has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ageological (X = Date, Y = Severity)
Ageological cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BHP (X = Date, Y = Severity)
BHP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ageological
BHP
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: *.*.