Comparison Overview

Broadcom

VS

onsemi

Broadcom

3401 Hillview Ave, Palo Alto, California, US, 94304
Last Update: 2025-12-11
Between 750 and 799

A global infrastructure technology leader built on more than 60 years of innovation, collaboration and engineering excellence.

NAICS: 3344
NAICS Definition: Semiconductor and Other Electronic Component Manufacturing
Employees: 53,946
Subsidiaries: 15
12-month incidents
2
Known data breaches
1
Attack type number
3

onsemi

5701 N. Pima Rd, Scottsdale, Arizona, 85250, US
Last Update: 2025-12-09
Between 750 and 799

onsemi (Nasdaq: ON) is driving disruptive innovations to help build a better future. With a focus on automotive and industrial end-markets, the company is accelerating change in megatrends such as vehicle electrification and safety, sustainable energy grids, industrial automation, and 5G and cloud infrastructure. With a highly differentiated and innovative product portfolio, onsemi creates intelligent power and sensing technologies that solve the world’s most complex challenges and leads the way in creating a safer, cleaner, and smarter world. Learn more about onsemi at www.onsemi.com.

NAICS: 3344
NAICS Definition: Semiconductor and Other Electronic Component Manufacturing
Employees: 15,245
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/broadcom.jpeg
Broadcom
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/on-semiconductor.jpeg
onsemi
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
Broadcom
100%
Compliance Rate
0/4 Standards Verified
onsemi
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Semiconductor Manufacturing Industry Average (This Year)

Broadcom has 150.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Semiconductor Manufacturing Industry Average (This Year)

No incidents recorded for onsemi in 2025.

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

Broadcom cyber incidents detection timeline including parent company and subsidiaries

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

onsemi cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/broadcom.jpeg
Broadcom
Incidents

Date Detected: 6/2025
Type:Ransomware
Attack Vector: Zero-Day Exploit (CVE-2025-61882, CVE-2025-21884), Unauthenticated HTTP Requests, Data Exfiltration
Motivation: Financial Gain (Ransomware Extortion)
Blog: Blog

Date Detected: 5/2025
Type:Ransomware
Attack Vector: zero-day vulnerability in Oracle E-Business Suite, arbitrary code execution, lateral movement, credential theft, data exfiltration
Motivation: financial gain (ransomware), data theft for extortion, disruption of high-value enterprise targets
Blog: Blog

Date Detected: 9/2024
Type:Ransomware
Attack Vector: third-party vendor (BSH, a regional partner of ADP)
Motivation: financial gain, data theft
Blog: Blog
https://images.rankiteo.com/companyimages/on-semiconductor.jpeg
onsemi
Incidents

No Incident

FAQ

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

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

In the current year, Broadcom company has reported more cyber incidents than onsemi company.

Broadcom company has confirmed experiencing a ransomware attack, while onsemi company has not reported such incidents publicly.

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

Neither onsemi company nor Broadcom company has reported experiencing targeted cyberattacks publicly.

Broadcom company has disclosed at least one vulnerability, while onsemi company has not reported such incidents publicly.

Neither Broadcom nor onsemi holds any compliance certifications.

Neither company holds any compliance certifications.

Broadcom company has more subsidiaries worldwide compared to onsemi company.

Broadcom company employs more people globally than onsemi company, reflecting its scale as a Semiconductor Manufacturing.

Neither Broadcom nor onsemi holds SOC 2 Type 1 certification.

Neither Broadcom nor onsemi holds SOC 2 Type 2 certification.

Neither Broadcom nor onsemi holds ISO 27001 certification.

Neither Broadcom nor onsemi holds PCI DSS certification.

Neither Broadcom nor onsemi holds HIPAA certification.

Neither Broadcom nor onsemi 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