Comparison Overview
Echo Electric (formerly Richards Electric)

Echo Electric (formerly Richards Electric)
4620 Reading Rd, Cincinnati, Ohio, US
Last Update: 02/04/2026
Richards Electric has been helping its customers power homes, businesses and cities by supplying quality electrical products and exceptional customer service ever since Richard Misrach opened the company's doors in 1937. Over eighty years later, Richards maintains the s...

Porsche Holding
Louise-Piëch-Straße 2, Salzburg, AT
Last Update: 31/03/2026
Porsche Holding Salzburg is the largest and most successful automotive distributor in Europe. Our roots are in Salzburg, but we now also operate in 29 countries on three continents. Our core expertise: global automotive distribution. Our business divisions: automotive w...
Compliance Ranges Comparison

Echo Electric (formerly Richards Electric)







Porsche Holding






Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Echo Electric (formerly Richards Electric) in 2026.
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Porsche Holding in 2026.
Incident History - Echo Electric (formerly Richards Electric) (X = Date, Y = Severity)
Echo Electric (formerly Richards Electric) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Porsche Holding (X = Date, Y = Severity)
Porsche Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Echo Electric (formerly Richards Electric)

Porsche Holding
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.