Comparison Overview
e& Egypt

e& Egypt
Fifth Setlment, Cairo, EG, 12411
Last Update: 06/09/2026
Building on 17 years of technology excellence in the Egyptian market, and in our relentless quest to bring you more and better services, etisalat by e& in Egypt has now evolved into the digital telco of the future. Covering and serving 99% of the inhabited areas in Eg...

Jio
Reliance Corporate Park, Navi Mumbai, 400701, IN
Last Update: 08/09/2026
Make a new start. A start that will build beautiful relationships, shape millions of ideas. Enable a new way to live, learn, work and play. At Jio, we build products and services of the future to empower billions of Indians make their dreams a reality. Jio is about YO...
Compliance Ranges Comparison

e& Egypt







Jio






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for e& Egypt in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Jio in 2026.
Incident History - e& Egypt (X = Date, Y = Severity)
e& Egypt cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jio (X = Date, Y = Severity)
Jio cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

e& Egypt

Jio
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.