Comparison Overview

Qualcomm

VS

Telstra

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

Telstra

400 George St, Sydney, NSW, 2000, AU
Last Update: 2025-12-09

We believe it’s people who give purpose to our technology. So we’re committed to staying close to our customers and providing them the best experience. And delivering the best tech. On the best network. Because our purpose is to build a connected future so everyone can thrive. We build technology and content solutions that are simple and easy to use, including Australia’s largest and fastest national mobile network. That’s why we strive to serve and know our customers better than anyone else – offering a choice of not just digital connection, but digital content as well. And that’s why we have an international presence spanning 15 countries, including China. In the 21st century, opportunity belongs to connected businesses, governments, communities and individuals. As Australia’s leading telecommunications and information services company, Telstra is proud to be helping our customers improve the ways in which they live and work through connection. Be first to know about Telstra news, advice and offers, as well as updates on our people and partners: tel.st/subscribe

NAICS: 517
NAICS Definition: Telecommunications
Employees: 35,264
Subsidiaries: 4
12-month incidents
0
Known data breaches
2
Attack type number
3

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/telstra.jpeg
Telstra
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
Telstra
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 Telstra in 2025.

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

Qualcomm cyber incidents detection timeline including parent company and subsidiaries

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

Telstra 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/telstra.jpeg
Telstra
Incidents

Date Detected: 10/2022
Type:Breach
Blog: Blog

Date Detected: 05/2021
Type:Data Leak
Attack Vector: Unspecified
Motivation: Ransom
Blog: Blog

Date Detected: 07/2018
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

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

Telstra company has faced a higher number of disclosed cyber incidents historically compared to Qualcomm company.

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

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

Telstra company has disclosed at least one data breach, while Qualcomm company has not reported such incidents publicly.

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

Both Qualcomm company and Telstra company have disclosed vulnerabilities.

Neither Qualcomm nor Telstra holds any compliance certifications.

Neither company holds any compliance certifications.

Telstra company has more subsidiaries worldwide compared to Qualcomm company.

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

Neither Qualcomm nor Telstra holds SOC 2 Type 1 certification.

Neither Qualcomm nor Telstra holds SOC 2 Type 2 certification.

Neither Qualcomm nor Telstra holds ISO 27001 certification.

Neither Qualcomm nor Telstra holds PCI DSS certification.

Neither Qualcomm nor Telstra holds HIPAA certification.

Neither Qualcomm nor Telstra 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.

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
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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
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."

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
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.

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
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).

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