Comparison Overview
SIS Global, Saudi HQ

SIS Global, Saudi HQ
King Fahad Road, Riyadh , Saudi Arabia, Riyadh, SA, 16511
Last Update: 13/03/2026
Welcome to SIS Global: Uniting Intelligent Solutions with Inspired Services Established in 2007 in Riyadh, Saudi Arabia, SIS Global is a testament to Saudi ingenuity and entrepreneurial spirit. With a foundation built on the creativity of our people, the efficiency of o...

Transcom
Hälsingegatan 40, 15th floor, Stockholm, SE-104 30, SE
Last Update: 02/04/2026
Transcom provides digitally enhanced customer experience (CX) services to some of the world's most ambitious brands. More than 300 clients globally, including disruptive e-commerce players, category redefining fintechs, and technology legends rely on us for on-, off-, a...
Compliance Ranges Comparison

SIS Global, Saudi HQ







Transcom






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

SIS Global, Saudi HQ

Transcom
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)