Comparison Overview

Honda

VS

Nissan Motor Corporation

Honda

2-1-1 Minamiaoyama Minato-ku, Tokyo 107-8556, JP
Last Update: 2025-11-20
Between 800 and 849

Honda is a global mobility company primarily known as a manufacturer of automobiles, motorcycles, power products and aircraft.

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

Nissan Motor Corporation

1-1, Takashima 1-chome,, None, Yokohama-shi, Kanagawa, JP, 220-8686
Last Update: 2025-11-27
Between 600 and 649

Nissan Motor Corporation is a global car manufacturer that sells a full line of vehicles under the Nissan and INFINITI brands. Nissan’s global headquarters in Yokohama, Japan, manages operations in four regions: Japan-ASEAN, China, Americas, and AMIEO (Africa, Middle East, India, Europe & Oceania). For more information about our products, services and commitment to sustainable mobility, visit nissan-global.com. You can also follow us on Facebook, Instagram, Twitter and LinkedIn and see all our latest videos on YouTube.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 45,615
Subsidiaries: 7
12-month incidents
0
Known data breaches
3
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/honda.jpeg
Honda
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/nissan-motor-corporation.jpeg
Nissan Motor Corporation
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
Honda
100%
Compliance Rate
0/4 Standards Verified
Nissan Motor Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Honda in 2025.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Nissan Motor Corporation in 2025.

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

Honda cyber incidents detection timeline including parent company and subsidiaries

Incident History — Nissan Motor Corporation (X = Date, Y = Severity)

Nissan Motor Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/honda.jpeg
Honda
Incidents

No Incident

https://images.rankiteo.com/companyimages/nissan-motor-corporation.jpeg
Nissan Motor Corporation
Incidents

Date Detected: 12/2023
Type:Data Leak
Blog: Blog

Date Detected: 11/2023
Type:Breach
Blog: Blog

Date Detected: 6/2022
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog

FAQ

Honda company demonstrates a stronger AI Cybersecurity Score compared to Nissan Motor Corporation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Nissan Motor Corporation company has historically faced a number of disclosed cyber incidents, whereas Honda company has not reported any.

In the current year, Nissan Motor Corporation company and Honda company have not reported any cyber incidents.

Neither Nissan Motor Corporation company nor Honda company has reported experiencing a ransomware attack publicly.

Nissan Motor Corporation company has disclosed at least one data breach, while Honda company has not reported such incidents publicly.

Nissan Motor Corporation company has reported targeted cyberattacks, while Honda company has not reported such incidents publicly.

Neither Honda company nor Nissan Motor Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Honda nor Nissan Motor Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Nissan Motor Corporation company has more subsidiaries worldwide compared to Honda company.

Nissan Motor Corporation company employs more people globally than Honda company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Honda nor Nissan Motor Corporation holds SOC 2 Type 1 certification.

Neither Honda nor Nissan Motor Corporation holds SOC 2 Type 2 certification.

Neither Honda nor Nissan Motor Corporation holds ISO 27001 certification.

Neither Honda nor Nissan Motor Corporation holds PCI DSS certification.

Neither Honda nor Nissan Motor Corporation holds HIPAA certification.

Neither Honda nor Nissan Motor Corporation 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