Comparison Overview

EE

VS

vivo

EE

undefined, London , undefined, undefined, GB
Last Update: 2025-12-09
View Profile
Between 750 and 799
http://ee.co.uk

EE, part of BT Group, is the largest and most advanced mobile communications company in the UK, delivering mobile and fixed communications services to consumers. We run the UK's biggest and fastest mobile network, having pioneered the UK's first superfast 4G mobile service in October 2012 and was the first European operator to surpass 14 million 4G customers in December 2015. We have more than 550 shops across the UK and we’re dedicated to making EE an outstanding place to work for our 13,000 employees. Our 4G coverage reaches 80% of the UK geography and we have plans to extend 4G geographic coverage to 95% by 2020. We’ve received extensive independent recognition, including being ranked the UK's best overall network by RootMetrics®; Best Network at the 2015, 2016 and 2017 Mobile News Awards; Best Network at the Mobile Choice Consumer Awards 2016; Best Consumer Network at the 2015 & 2016 Mobile Industry Awards; as well as Fastest Network and Best Network Coverage at the 2017 uSwitch Mobile Awards.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 11,299
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
2
View Profile

vivo

No.283 BBK Road, Wusha, Chang'an, Dongguan, Guangdong, China, Dongguan, 523860, CN
Last Update: 2025-12-09
Between 750 and 799
http://www.vivo.com/en

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/ee-uk.jpeg
EE
—
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
EE
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)

No incidents recorded for EE in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for vivo in 2025.

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

EE 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/ee-uk.jpeg
EE
Incidents

Date Detected: 12/2024
Type:Ransomware
Blog: Blog

Date Detected: 05/2018
Type:Data Leak
Attack Vector: Exposed Default Password
Motivation: Unintentional Exposure
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 EE company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

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

In the current year, vivo company and EE company have not reported any cyber incidents.

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

Neither vivo company nor EE company has reported experiencing a data breach publicly.

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

Neither EE company nor vivo company has reported experiencing or disclosing vulnerabilities publicly.

Neither EE nor vivo holds any compliance certifications.

Neither company holds any compliance certifications.

EE company has more subsidiaries worldwide compared to vivo company.

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

Neither EE nor vivo holds SOC 2 Type 1 certification.

Neither EE nor vivo holds SOC 2 Type 2 certification.

Neither EE nor vivo holds ISO 27001 certification.

Neither EE nor vivo holds PCI DSS certification.

Neither EE nor vivo holds HIPAA certification.

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