Comparison Overview
Swiss Re Risk Data Solutions
Swiss Re Risk Data Solutions
Mythenquai 50/60, Zurich, Zurich, CH, 8022
Last Update: 02/04/2026
Risk Data Solutions equips clients with integrated intelligence to navigate uncertainty and act decisively. We combine Swiss Re’s data, models, technology and advisory into one connected experience designed around the realities insurers, corporates and the public sector...
USI Insurance Services
100 Summit Lake Drive, Valhalla, 10595, US
Last Update: 04/04/2026
USI is one of the largest insurance brokerage and consulting firms in the world, delivering property and casualty, employee benefits, personal risk, program and retirement solutions to large risk management clients, middle market companies, smaller firms and individuals...
Compliance Ranges Comparison
Swiss Re Risk Data Solutions
USI Insurance Services
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Swiss Re Risk Data Solutions in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for USI Insurance Services in 2026.
Incident History - Swiss Re Risk Data Solutions (X = Date, Y = Severity)
Swiss Re Risk Data Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - USI Insurance Services (X = Date, Y = Severity)
USI Insurance Services cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Swiss Re Risk Data Solutions
USI Insurance Services
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: *.*.