Comparison Overview

Comcast

VS

vivo

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

vivo

No.283 BBK Road, Wusha, Chang'an, Dongguan, Guangdong, China, Dongguan, 523860, CN
Last Update: 2025-11-21
Between 750 and 799

vivo is a technology company that creates great products based on a design-driven value, with smart devices and intelligent services as its core. The company aims to build a bridge between humans and the digital world. Through unique creativity, vivo provides users with an increasingly convenient mobile and digital life. vivo has over 18,000 employees across the globe. While bringing together and developing the best local talents to deliver excellence, vivo is supported by a network of 10 R&D centers in Shenzhen, Dongguan, Nanjing, Beijing, Hangzhou, Shanghai, Xi'an, Taipei, Tokyo and San Diego, focusing on the development of state-of-the-art consumer technologies, including 5G, artificial intelligence, industrial design, imaging system and other up-and-coming technologies. vivo has also set up 7 production bases (including brand-authorized manufacturing centers), across China, South- and Southeast Asia, and more regions, with an annual production capacity of nearly 200 million smartphones. As of now, vivo has branched out its sales network across more than 60 countries and regions, and is winning more than 400 million users worldwide with its superior products and services. Following the company's core values, which include Benfen, design-driven value, user-orientation, continuous learning and team spirit. vivo has implemented a sustainable development strategy, with the vision of developing into a healthier, more sustainable world-class corporation. Official Site: www.vivo.com/en Facebook: @vivoGlobal Instagram: @vivo_global

NAICS: 517
NAICS Definition: Telecommunications
Employees: 18,472
Subsidiaries: 4
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/vivo-smartphone.jpeg
vivo
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
vivo
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 vivo in 2025.

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

Comcast cyber incidents detection timeline including parent company and subsidiaries

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

vivo 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/vivo-smartphone.jpeg
vivo
Incidents

No Incident

FAQ

vivo 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 vivo company has not reported any.

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

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

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

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

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

Neither Comcast nor vivo holds any compliance certifications.

Neither company holds any compliance certifications.

Comcast company has more subsidiaries worldwide compared to vivo company.

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

Neither Comcast nor vivo holds SOC 2 Type 1 certification.

Neither Comcast nor vivo holds SOC 2 Type 2 certification.

Neither Comcast nor vivo holds ISO 27001 certification.

Neither Comcast nor vivo holds PCI DSS certification.

Neither Comcast nor vivo holds HIPAA certification.

Neither Comcast nor vivo 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