Comparison Overview
Thirdera

Thirdera
370 Interlocken Blvd, Broomfield, 80021, US
Last Update: 07/12/2025
Thirdera, founded in 2021, was acquired by Cognizant in 2024 and is now the Cognizant ServiceNow Business Group. Prior to being acquired, Thirdera was one of the largest and most credentialed ServiceNow partners globally, enabling customers to maximize the value of the...

IGT Solutions
Sector 32 Road, Plot 49, Echelon Building, Gurugram, Haryana, IN, 122 001
Last Update: 01/04/2026
IGT Solutions is a next-gen customer experience (CX) company, defining and delivering AI-led transformative experiences for the global and most innovative brands using digital technologies. With the combination of Digital and Human Intelligence, IGT becomes the preferre...
Compliance Ranges Comparison

Thirdera







IGT Solutions






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Thirdera in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for IGT Solutions in 2026.
Incident History - Thirdera (X = Date, Y = Severity)
Thirdera cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IGT Solutions (X = Date, Y = Severity)
IGT Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Thirdera

IGT Solutions
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.