Comparison Overview

AMD

VS

onsemi

AMD

2485 Augustine Drive, Santa Clara, California, US, 95054
Last Update: 2025-12-19
Between 800 and 849

We care deeply about transforming lives with AMD technology to enrich our industry, our communities, and the world. Our mission is to build great products that accelerate next-generation computing experiences – the building blocks for the data center, artificial intelligence, PCs, gaming and embedded. Underpinning our mission is the AMD culture. We push the limits of innovation to solve the world’s most important challenges. We strive for execution excellence while being direct, humble, collaborative, and inclusive of diverse perspectives. AMD together we advance_

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

onsemi

5701 N. Pima Rd, Scottsdale, Arizona, 85250, US
Last Update: 2025-12-17
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/amd.jpeg
AMD
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
AMD
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)

AMD has 185.71% 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 — AMD (X = Date, Y = Severity)

AMD 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/amd.jpeg
AMD
Incidents

Date Detected: 10/2025
Type:Vulnerability
Attack Vector: Local (Admin-Privileged Hypervisor), Memory Manipulation
Blog: Blog

Date Detected: 3/2025
Type:Vulnerability
Attack Vector: High Privilege Attack
Blog: Blog

Date Detected: 6/2024
Type:Vulnerability
Attack Vector: Improper signature verification in CPU ROM microcode patch loader
Blog: Blog
https://images.rankiteo.com/companyimages/on-semiconductor.jpeg
onsemi
Incidents

No Incident

FAQ

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

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

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

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

Neither onsemi company nor AMD company has reported experiencing a data breach publicly.

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

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

Neither AMD nor onsemi holds any compliance certifications.

Neither company holds any compliance certifications.

onsemi company has more subsidiaries worldwide compared to AMD company.

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

Neither AMD nor onsemi holds SOC 2 Type 1 certification.

Neither AMD nor onsemi holds SOC 2 Type 2 certification.

Neither AMD nor onsemi holds ISO 27001 certification.

Neither AMD nor onsemi holds PCI DSS certification.

Neither AMD nor onsemi holds HIPAA certification.

Neither AMD nor onsemi holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

Risk Information
cvss4
Base: 9.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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