Comparison Overview
Siemens eMobility

Siemens eMobility
Siemenspromenade, Erlangen, Bavaria, DE, 91058
Last Update: 21/06/2026
eMobility is crucial for achieving global climate goals. Siemens eMobility is dedicated to integrating it into everyday life, contributing to a more sustainable future. Our portfolio covers all aspects of smart and efficient DC charging infrastructure, including IoT-con...

Keysight Technologies
1400 Fountaingrove Pkwy, Santa Rosa, California, US, 95403
Last Update: 02/04/2026
Keysight empowers innovators to explore, design, and bring world-changing technologies to life. As the industry’s premier global innovation partner, Keysight’s software-centric solutions serve engineers across the design and development environment, enabling them to del...
Compliance Ranges Comparison

Siemens eMobility







Keysight Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Siemens eMobility in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Keysight Technologies in 2026.
Incident History - Siemens eMobility (X = Date, Y = Severity)
Siemens eMobility cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Keysight Technologies (X = Date, Y = Severity)
Keysight Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Siemens eMobility

Keysight Technologies
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.