Comparison Overview

e& UAE

VS

Vivo (Telefônica Brasil)

e& UAE

Sheikh Rashid Bin Saeed Al Maktoum Street, Abu Dhabi, AE, 3838
Last Update: 2025-11-27
Between 800 and 849

(Formerly etisalat UAE) For more than four decades, we have connected people and now we’ve evolved to become the digital telco of the future. Our mission is to grow, transform and excel as the region’s technology leader while enhancing digital customer experience and operation agility. e& UAE offers digital experiences that cater to your new lifestyle and demands beyond just telecom and are not limited to gaming, health, and insurance. We will continue to be your trusted partner and advisor, enabling connectivity and everything beyond, accelerating the digital world and pioneering future-forward spaces like private networks, autonomous vehicles, and AI. Together, we embark on this new era of e& UAE and step into a new world of possibilities. We are etisalat and so much more.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 44,506
Subsidiaries: 18
12-month incidents
0
Known data breaches
0
Attack type number
0

Vivo (Telefônica Brasil)

Avenida Eng. Luís Carlos Berrini, 1376, São Paulo, SP, BR, 04571 - 000
Last Update: 2025-11-27
Between 750 and 799

Vivo (Telefônica Brasil) is part of the Telefónica Group and with more than 94 million customers, of which 75 million mobile and 19 million fixed, we are the largest telecommunications company in Brazil, with nationwide presence and a complete, convergent portfolio of products, combining fixed, mobile and digital services. Our purpose is “Digitalize to Bring Closer”, helping to build a digital nation and transforming the life of our customers. More and more, we connect people and things with Fiber, 4G and 4.5G and cover more cities with the network quality that only Vivo has. Today, we cover around 90% of the population with 4G and are accelerating the launch of cities with 4.5G, using carrier aggregation technology. In the fixed operation, we ended 2019 with 21 million homes-passed (HPs) with fiber optic technology, of which 11 million HPs with FTTH (fiber to the home). In addition, all cities with FTTH technology also offer TV over fiber (IPTV), aiming to offer the best speed and experience to our consumers. At Vivo, we also do more than just telecommunications. Within the Group, we have the Telefônica Vivo Foundation, that is committed to making education a priority, developing projects that are based on human potential and use technology as an instrument in favor of inclusion and digital culture.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 37,866
Subsidiaries: 27
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/eanduae.jpeg
e& UAE
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-telefonicabr.jpeg
Vivo (Telefônica Brasil)
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
e& UAE
100%
Compliance Rate
0/4 Standards Verified
Vivo (Telefônica Brasil)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for e& UAE in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Vivo (Telefônica Brasil) in 2025.

Incident History — e& UAE (X = Date, Y = Severity)

e& UAE cyber incidents detection timeline including parent company and subsidiaries

Incident History — Vivo (Telefônica Brasil) (X = Date, Y = Severity)

Vivo (Telefônica Brasil) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/eanduae.jpeg
e& UAE
Incidents

No Incident

https://images.rankiteo.com/companyimages/vivo-telefonicabr.jpeg
Vivo (Telefônica Brasil)
Incidents

Date Detected: 5/2025
Type:Ransomware
Attack Vector: Internal Jira development and ticketing server
Motivation: Ransom
Blog: Blog

FAQ

e& UAE company demonstrates a stronger AI Cybersecurity Score compared to Vivo (Telefônica Brasil) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Vivo (Telefônica Brasil) company has historically faced a number of disclosed cyber incidents, whereas e& UAE company has not reported any.

In the current year, Vivo (Telefônica Brasil) company has reported more cyber incidents than e& UAE company.

Vivo (Telefônica Brasil) company has confirmed experiencing a ransomware attack, while e& UAE company has not reported such incidents publicly.

Neither Vivo (Telefônica Brasil) company nor e& UAE company has reported experiencing a data breach publicly.

Neither Vivo (Telefônica Brasil) company nor e& UAE company has reported experiencing targeted cyberattacks publicly.

Neither e& UAE company nor Vivo (Telefônica Brasil) company has reported experiencing or disclosing vulnerabilities publicly.

Neither e& UAE nor Vivo (Telefônica Brasil) holds any compliance certifications.

Neither company holds any compliance certifications.

Vivo (Telefônica Brasil) company has more subsidiaries worldwide compared to e& UAE company.

e& UAE company employs more people globally than Vivo (Telefônica Brasil) company, reflecting its scale as a Telecommunications.

Neither e& UAE nor Vivo (Telefônica Brasil) holds SOC 2 Type 1 certification.

Neither e& UAE nor Vivo (Telefônica Brasil) holds SOC 2 Type 2 certification.

Neither e& UAE nor Vivo (Telefônica Brasil) holds ISO 27001 certification.

Neither e& UAE nor Vivo (Telefônica Brasil) holds PCI DSS certification.

Neither e& UAE nor Vivo (Telefônica Brasil) holds HIPAA certification.

Neither e& UAE nor Vivo (Telefônica Brasil) 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