Comparison Overview

Totalplay

VS

stc

Totalplay

Avenida San Jerónimo 252 Álvaro Obregón, Mexico City 01090, MX
Last Update: 2025-12-09
Between 750 and 799

Somos una empresa orgullosamente mexicana, líder en tecnología, telecomunicaciones y entretenimiento. Estamos siempre a la vanguardia con el objetivo de llevar a nuestros clientes lo mejor en conectividad, ya sea para que estén cerca de los que más quieren ó puedan alcanzar el éxito profesional gracias a la velocidad que brinda la tecnología de fibra óptica. Nuestro impulso es el equipo que hemos formado, personas con talento, iniciativa, entusiastas y apasionados, que buscan siempre caminar unidos para llevar a más de 20 ciudades de la República Mexicana un servicio de excelencia. Queremos que nuestros clientes sean parte del camino al futuro y vivan al máximo la experiencia de la plataforma de conectividad y entretenimiento total.

NAICS: 517
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

stc

King Abdul Aziz Complex, Mursalat, Riyadh, Riyadh, SA
Last Update: 2025-12-09

We are a forward-focused digital champion always been focused on innovation and evolution. Our purpose is to create and bring greater dimension and richness to people’s personal and professional lives.  With stc, You will always be empowered to focus on delivering what’s next through collaborative and agile ways of working, and a culture that is open to fresh ideas. Transforming the future through impactful digital solutions and mega-projects while fostering our commitment to sustainability. Join a people-centric environment; that cares about maximizing your wellbeing, and is committed to unlocking your potential.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 17,035
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/totalplay.jpeg
Totalplay
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/stc.jpeg
stc
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Totalplay
100%
Compliance Rate
0/4 Standards Verified
stc
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Totalplay in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for stc in 2025.

Incident History — Totalplay (X = Date, Y = Severity)

Totalplay cyber incidents detection timeline including parent company and subsidiaries

Incident History — stc (X = Date, Y = Severity)

stc cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/totalplay.jpeg
Totalplay
Incidents

No Incident

https://images.rankiteo.com/companyimages/stc.jpeg
stc
Incidents

No Incident

FAQ

stc company demonstrates a stronger AI Cybersecurity Score compared to Totalplay company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, stc company has disclosed a higher number of cyber incidents compared to Totalplay company.

In the current year, stc company and Totalplay company have not reported any cyber incidents.

Neither stc company nor Totalplay company has reported experiencing a ransomware attack publicly.

Neither stc company nor Totalplay company has reported experiencing a data breach publicly.

Neither stc company nor Totalplay company has reported experiencing targeted cyberattacks publicly.

Neither Totalplay company nor stc company has reported experiencing or disclosing vulnerabilities publicly.

Neither Totalplay nor stc holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Totalplay company nor stc company has publicly disclosed detailed information about the number of their subsidiaries.

stc company employs more people globally than Totalplay company, reflecting its scale as a Telecommunications.

Neither Totalplay nor stc holds SOC 2 Type 1 certification.

Neither Totalplay nor stc holds SOC 2 Type 2 certification.

Neither Totalplay nor stc holds ISO 27001 certification.

Neither Totalplay nor stc holds PCI DSS certification.

Neither Totalplay nor stc holds HIPAA certification.

Neither Totalplay nor stc holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N