Comparison Overview
Trust + Safety

Trust + Safety
New Braunfels, US
Last Update: 24/04/2026
Platforms and businesses are increasingly exposed to a number of serious trust and safety risks. A robust moderation system powered by a vigilant workforce is the only solution to protecting users everywhere. At TaskUs, we understand the growing need for Trust + Safety...

ResultsCX
1700 Markley St, Suite 210, Norristown, Pennsylvania, US, 19401
Last Update: 05/04/2026
ResultsCX is a leading provider of transformational Customer Experience Management (CXM) solutions to 75+ global brands, including Fortune 100 and 500 companies. For 30+ years, we have been driving superior customer and business outcomes for brands across Healthcare, Me...
Compliance Ranges Comparison

Trust + Safety







ResultsCX






Benchmark & Cyber Underwriting Signals
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for Trust + Safety in 2026.
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for ResultsCX in 2026.
Incident History - Trust + Safety (X = Date, Y = Severity)
Trust + Safety cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ResultsCX (X = Date, Y = Severity)
ResultsCX cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Trust + Safety

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