Comparison Overview

Qualcomm

VS

TELUS

Qualcomm

Qualcomm, San Diego, CA, 92121, US
Last Update: 2025-12-09
Between 800 and 849

Delivering intelligent computing everywhere.

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

TELUS

510 West Georgia St., Vancouver, British Columbia, V6B 0M3, CA
Last Update: 2025-12-09
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/qualcomm.jpeg
Qualcomm
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
Qualcomm
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 Qualcomm in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for TELUS in 2025.

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

Qualcomm 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/qualcomm.jpeg
Qualcomm
Incidents

Date Detected: 8/2024
Type:Vulnerability
Attack Vector: GPU Driver Exploitation
Motivation: Full Device Control
Blog: Blog
https://images.rankiteo.com/companyimages/telus.jpeg
TELUS
Incidents

No Incident

FAQ

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

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

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

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

Neither TELUS company nor Qualcomm company has reported experiencing a data breach publicly.

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

Qualcomm company has disclosed at least one vulnerability, while TELUS company has not reported such incidents publicly.

Neither Qualcomm nor TELUS holds any compliance certifications.

Neither company holds any compliance certifications.

TELUS company has more subsidiaries worldwide compared to Qualcomm company.

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

Neither Qualcomm nor TELUS holds SOC 2 Type 1 certification.

Neither Qualcomm nor TELUS holds SOC 2 Type 2 certification.

Neither Qualcomm nor TELUS holds ISO 27001 certification.

Neither Qualcomm nor TELUS holds PCI DSS certification.

Neither Qualcomm nor TELUS holds HIPAA certification.

Neither Qualcomm nor TELUS holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N