Comparison Overview

Jio

VS

TELUS

Jio

Reliance Corporate Park, Navi Mumbai, Maharashtra, 400701, IN
Last Update: 2025-11-20
Between 750 and 799

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 YOU. Join the movement to make India Digital. Chat on MyJio App: http://tiny.jio.com/chat1 Chat on WhatsApp: http://tiny.jio.com/LiveChat

NAICS: 517
NAICS Definition: Telecommunications
Employees: 97,138
Subsidiaries: 3
12-month incidents
0
Known data breaches
1
Attack type number
2

TELUS

510 West Georgia St., Vancouver, British Columbia, V6B 0M3, CA
Last Update: 2025-11-20
Between 750 and 799

At TELUS, our purpose-driven team works together every day to innovate and do good. From providing technology solutions that make our lives safer and easier, to supporting those who need it most, our inclusive, spirited and giving people are passionate about empowering our customers, communities and each other to thrive in our digital world. A company that helps you be your best self at home and at work: Find a place where you truly belong, your opinions are valued and you can be your best self. A career that ignites your full potential: Get the guidance and support you need to explore your interests, build your skills and get where you want to go. A culture that goes beyond the expected to strengthen communities and the planet: Seize the opportunity to make a difference in our communities and do good for our planet as part of our purpose-driven team. An innovative team committed to solving complex, real world problems: Join a digitally-enabled workforce that’s pushing the boundaries to create sustainable change. Join us, and let’s make the future friendly, together www.telus.com/careers

NAICS: 517
NAICS Definition: Telecommunications
Employees: 34,521
Subsidiaries: 7
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/jio.jpeg
Jio
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/telus.jpeg
TELUS
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
Jio
100%
Compliance Rate
0/4 Standards Verified
TELUS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Jio in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for TELUS in 2025.

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

Jio cyber incidents detection timeline including parent company and subsidiaries

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

TELUS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jio.jpeg
Jio
Incidents

Date Detected: 05/2020
Type:Data Leak
Attack Vector: Unsecured Database
Blog: Blog

Date Detected: 07/2017
Type:Breach
Blog: Blog

Date Detected: 02/2017
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/telus.jpeg
TELUS
Incidents

No Incident

FAQ

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

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

In the current year, TELUS company and Jio company have not reported any cyber incidents.

Neither TELUS company nor Jio company has reported experiencing a ransomware attack publicly.

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

Neither TELUS company nor Jio company has reported experiencing targeted cyberattacks publicly.

Neither Jio company nor TELUS company has reported experiencing or disclosing vulnerabilities publicly.

Neither Jio nor TELUS holds any compliance certifications.

Neither company holds any compliance certifications.

TELUS company has more subsidiaries worldwide compared to Jio company.

Jio company employs more people globally than TELUS company, reflecting its scale as a Telecommunications.

Neither Jio nor TELUS holds SOC 2 Type 1 certification.

Neither Jio nor TELUS holds SOC 2 Type 2 certification.

Neither Jio nor TELUS holds ISO 27001 certification.

Neither Jio nor TELUS holds PCI DSS certification.

Neither Jio nor TELUS holds HIPAA certification.

Neither Jio nor TELUS 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