Comparison Overview
WSP en Chile

WSP en Chile
Avenida Las Condes 11700, Vitacura, Santiago, Región Metropolitana de Santiago, 7650002, CL
Last Update: 19/03/2026
WSP en una empresa líder en servicios profesionales de consultoría en recursos hídricos, ingeniería, medio ambiente y sustentabilidad. Somos consultores estratégicos y expertos técnicos. Nuestro equipo multidisciplinario incluye ingenieros en todas las especialidades, h...

SGS
Zugerstrasse 57, Baar, Zug, CH, 6340
Last Update: 31/03/2026
SGS is the world’s leading Testing, Inspection and Certification company. We operate a network of over 2,500 laboratories and business facilities across 115 countries, supported by a team of 99,500 dedicated professionals. With over 145 years of service excellence, we c...
Compliance Ranges Comparison

WSP en Chile







SGS






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for WSP en Chile in 2026.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for SGS in 2026.
Incident History - WSP en Chile (X = Date, Y = Severity)
WSP en Chile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SGS (X = Date, Y = Severity)
SGS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

WSP en Chile

SGS
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: *.*.