Comparison Overview

Mercedes-Benz USA

VS

BYD

Mercedes-Benz USA

303 Perimeter Center North, Atlanta, GA, US, 30346
Last Update: 2025-11-26
Between 750 and 799

Mercedes-Benz USA, LLC (MBUSA), a Daimler Company, is responsible for the Distribution and Marketing of Mercedes-Benz and smart products in the United States. MBUSA was founded in 1965 and prior to that Mercedes-Benz cars were sold in the United States by Mercedes-Benz Car Sales, Inc., a subsidiary of the Studebaker-Packard corporation. Today MBUSA has over 300 dealerships with more than 1400 employees. For employment opportunities please visit: http://bit.ly/2tFzlOV. For information on how to get the most out of your Mercedes-Benz vehicle, visit the Owners'​ Support instructional videos section of our site: http://www.mbusa.com/mercedes/owners/videos

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 11,599
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

BYD

No.3009, BYD Road, Pingshan, Shenzhen, Guangdong, 518118, CN
Last Update: 2025-11-27
Between 800 and 849

Established in 1995, BYD is a top high-tech enterprise in China specializing in IT, automobile, and new energy.BYD is the largest supplier of rechargeable batteries in the globe, and has the largest market share for Nickel-cadmium batteries, handset Li-ion batteries, cell-phone chargers and keypads worldwide. It also has the second largest market share for cell-phone shells in the globe. BYD Auto becomes the most innovative independent national auto brand and leads the field of electric vehicles with unique technologies. In the field of new energy, BYD has developed green products such as solar farm, battery energy storage station, electric vehicle, and LED, etc. It will continue to lead the new energy revolution in the world!

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 15,445
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/mercedes-benz-usa.jpeg
Mercedes-Benz USA
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/byd.jpeg
BYD
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
Mercedes-Benz USA
100%
Compliance Rate
0/4 Standards Verified
BYD
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Mercedes-Benz USA in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for BYD in 2025.

Incident History — Mercedes-Benz USA (X = Date, Y = Severity)

Mercedes-Benz USA cyber incidents detection timeline including parent company and subsidiaries

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

BYD cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mercedes-benz-usa.jpeg
Mercedes-Benz USA
Incidents

No Incident

https://images.rankiteo.com/companyimages/byd.jpeg
BYD
Incidents

No Incident

FAQ

BYD company demonstrates a stronger AI Cybersecurity Score compared to Mercedes-Benz USA company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, BYD company has disclosed a higher number of cyber incidents compared to Mercedes-Benz USA company.

In the current year, BYD company and Mercedes-Benz USA company have not reported any cyber incidents.

Neither BYD company nor Mercedes-Benz USA company has reported experiencing a ransomware attack publicly.

Neither BYD company nor Mercedes-Benz USA company has reported experiencing a data breach publicly.

Neither BYD company nor Mercedes-Benz USA company has reported experiencing targeted cyberattacks publicly.

Neither Mercedes-Benz USA company nor BYD company has reported experiencing or disclosing vulnerabilities publicly.

Neither Mercedes-Benz USA nor BYD holds any compliance certifications.

Neither company holds any compliance certifications.

Mercedes-Benz USA company has more subsidiaries worldwide compared to BYD company.

BYD company employs more people globally than Mercedes-Benz USA company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Mercedes-Benz USA nor BYD holds SOC 2 Type 1 certification.

Neither Mercedes-Benz USA nor BYD holds SOC 2 Type 2 certification.

Neither Mercedes-Benz USA nor BYD holds ISO 27001 certification.

Neither Mercedes-Benz USA nor BYD holds PCI DSS certification.

Neither Mercedes-Benz USA nor BYD holds HIPAA certification.

Neither Mercedes-Benz USA nor BYD 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