Comparison Overview

Comcast

VS

Telmex

Comcast

None, None, Philadelphia, PA, US, 19103
Last Update: 2025-11-27

Welcome to Comcast. From the connectivity and platforms we provide to the content and experiences we create, we bring people together, globally. Our people think the world of our work, and that’s why our work is the best in the world.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 60,212
Subsidiaries: 13
12-month incidents
1
Known data breaches
10
Attack type number
4

Telmex

Parque Vía 190, Ciudad de México, México, 06500, MX
Last Update: 2025-11-27
Between 750 and 799

TELMEX, la empresa líder de telecomunicaciones y servicios TI en México, ha realizado importantes inversiones para desarrollar la plataforma tecnológica más robusta y vanguardista del país, que le permite ofrecer la más amplia gama de soluciones, con los mayores estándares de calidad, seguridad, confiabilidad y competitividad; por ello, es el mejor socio estratégico en servicios avanzados de telecomunicaciones y TI. Las Soluciones TI de TELMEX van desde la Conectividad hasta Servicios de Nube, Centros de Datos, Ciberseguridad, Colaboración y Soluciones de Negocio. Un portafolio enfocado a cubrir las necesidades y proporcionar atención en infraestructura y procesos, lo que permite a los clientes aprovechar al máximo su inversión en tecnología, mientras evolucionan hacia nuevos sistemas y plataformas como servicio. TELMEX permite desarrollar e implementar proyectos en empresas de cualquier tamaño y en cualquier vertical de industria, ofreciendo soluciones integrales, innovadoras y de clase mundial, a través de tecnología de punta; brindando conectividad soportada por la mayor cobertura nacional e internacional y anchos de banda que garantizan la continuidad de las operaciones de sus clientes.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 13,261
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/comcast.jpeg
Comcast
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/telmex.jpeg
Telmex
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
Comcast
100%
Compliance Rate
0/4 Standards Verified
Telmex
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

Comcast has 69.49% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Telmex in 2025.

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

Comcast cyber incidents detection timeline including parent company and subsidiaries

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

Telmex cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/comcast.jpeg
Comcast
Incidents

Date Detected: 11/2025
Type:Breach
Blog: Blog

Date Detected: 8/2024
Type:Breach
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: unauthorized access to vendor (FBCS) network
Blog: Blog
https://images.rankiteo.com/companyimages/telmex.jpeg
Telmex
Incidents

No Incident

FAQ

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

Comcast company has historically faced a number of disclosed cyber incidents, whereas Telmex company has not reported any.

In the current year, Comcast company has reported more cyber incidents than Telmex company.

Comcast company has confirmed experiencing a ransomware attack, while Telmex company has not reported such incidents publicly.

Comcast company has disclosed at least one data breach, while the other Telmex company has not reported such incidents publicly.

Neither Telmex company nor Comcast company has reported experiencing targeted cyberattacks publicly.

Comcast company has disclosed at least one vulnerability, while Telmex company has not reported such incidents publicly.

Neither Comcast nor Telmex holds any compliance certifications.

Neither company holds any compliance certifications.

Comcast company has more subsidiaries worldwide compared to Telmex company.

Comcast company employs more people globally than Telmex company, reflecting its scale as a Telecommunications.

Neither Comcast nor Telmex holds SOC 2 Type 1 certification.

Neither Comcast nor Telmex holds SOC 2 Type 2 certification.

Neither Comcast nor Telmex holds ISO 27001 certification.

Neither Comcast nor Telmex holds PCI DSS certification.

Neither Comcast nor Telmex holds HIPAA certification.

Neither Comcast nor Telmex holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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