Comparison Overview
Yusen Logistics
Yusen Logistics
Shinagawa Seaside Park Tower 4-12-4 Higashishinagawa, Shinagawa-ku, Tokyo, JP, 1400002
Last Update: 29/03/2026
Yusen Logistics is the insight-driven, customer-centric logistics partner to global business. We deliver this through an extended range of services from International Freight Forwarding and Contract Logistics to Supply Chain Solutions and Industry insights covering the ...
Amazon DSP
N/A
Last Update: 02/04/2026
Amazon Delivery Service Partner Programm Wir suchen praxisorientierte Unternehmer, die mit Leidenschaft großartige Teams aufbauen und entwickeln. Mit niedrigen Anlaufkosten, einer hohen Nachfrage, dem Zugang zu Technologien und dem umfassenden Logistik-Know-how von Amaz...
Compliance Ranges Comparison
Yusen Logistics
Amazon DSP
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Yusen Logistics in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Amazon DSP in 2026.
Incident History - Yusen Logistics (X = Date, Y = Severity)
Yusen Logistics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amazon DSP (X = Date, Y = Severity)
Amazon DSP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Yusen Logistics
Amazon DSP
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: *.*.