Comparison Overview

Telcel

VS

stc

Telcel

Lago Zurich, Granada, Distrito Federal, 11520, MX
Last Update: 2025-12-09
View Profile
Between 750 and 799
http://www.telcel.com

Telcel (Radiomóvil Dipsa) es subsidiaria de América Móvil, uno de los mayores proveedores de comunicaciones celulares de Latinoamérica, grupo líder con inversiones en telecomunicaciones en varios países del continente americano. Telcel es la empresa de telefonía celular líder en México. Nuestra solidez y estructura nos consolidan gracias a la especialización y actualización permanente de todas las personas que trabajamos en ella. Todos nosotros estamos comprometidos a satisfacer de manera eficaz y constante todas las necesidades de comunicación inalámbrica de nuestros clientes.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 15,551
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

stc

King Abdul Aziz Complex, Mursalat, Riyadh, Riyadh, SA
Last Update: 2025-12-09
Between 800 and 849
https://careers.stc.com.sa/#/

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/telcel.jpeg
Telcel
—
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
Telcel
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 Telcel in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for stc in 2025.

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

Telcel 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/telcel.jpeg
Telcel
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 Telcel company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

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

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

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

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

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

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

Neither Telcel nor stc holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

Neither Telcel nor stc holds SOC 2 Type 1 certification.

Neither Telcel nor stc holds SOC 2 Type 2 certification.

Neither Telcel nor stc holds ISO 27001 certification.

Neither Telcel nor stc holds PCI DSS certification.

Neither Telcel nor stc holds HIPAA certification.

Neither Telcel 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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
Description

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

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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."

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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.

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References
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).

Published
Date
2025-12-14
Updated
Date
2025-12-14
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
References