Comparison Overview
TP
TP
21, Rue Balzac, Paris, Île-de-France, FR, 75008
Last Update: 27/08/2026
We are TP Group. You’ve been calling us Teleperformance for almost 47 years. But in the AI era, the world has changed, and we had to change too to keep leading the digital business services market. We’re sharper, more modern, and even more empathetic. We are TP. Simple...
TaskUs
1650 Independence Dr, New Braunfels, 78132, US
Last Update: 01/04/2026
TaskUs delivers outsourced digital services that power the companies shaping the future. By combining specialized human talent and intelligent technology, we solve complex operational challenges for global category leaders within AI, autonomous vehicles (AV), robotics, ...
Compliance Ranges Comparison
TP
TaskUs
Benchmark & Cyber Underwriting Signals
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
No incidents recorded for TP in 2026.
Incidents vs Outsourcing and Offshoring Consulting Industry Avg (This Year)
TaskUs has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - TP (X = Date, Y = Severity)
TP cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TaskUs (X = Date, Y = Severity)
TaskUs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TP
TaskUs
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.