Comparison Overview
Accenture DACH

Accenture DACH
Campus Kronberg 1, Kronberg im Taunus, 61476, DE
Last Update: 02/04/2026
Über Accenture: Wir sind die weltweit führenden Berater für Strategie, Management, Digitalisierung, Technologie, Outsourcing und Business Transformation. Accenture bietet End-to-End-Lösungen – von der Strategie-Entwicklung über die Digitale Transformation bis hin zur o...

Verizon
One Verizon Way, Basking Ridge, 07920-1097, US
Last Update: 25/07/2026
We get you. You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. You’ll find all that here. Because we empower you. We power and empower how people live, work and play ...
Compliance Ranges Comparison

Accenture DACH







Verizon






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Accenture DACH in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Verizon has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - Accenture DACH (X = Date, Y = Severity)
Accenture DACH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Verizon (X = Date, Y = Severity)
Verizon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Accenture DACH

Verizon
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.