Comparison Overview

Toyota Motor Corporation

VS

Cummins Inc.

Toyota Motor Corporation

1 Toyota-Cho, None, Toyota City, Aichi Prefecture, JP, 471-8571
Last Update: 2025-11-20

Toyota Motor Corporation is a global automotive industry leader manufacturing vehicles in 27 countries or regions and marketing the company’s products in over 170 countries and regions. Founded in 1937 and headquartered in Toyota City, Japan, Toyota Motor Corporation employs nearly 350,000 people globally.

NAICS: 3361
NAICS Definition: Motor Vehicle Manufacturing
Employees: 31,153
Subsidiaries: 0
12-month incidents
2
Known data breaches
1
Attack type number
4

Cummins Inc.

500 Jackson St, Columbus, 47201, US
Last Update: 2025-11-21
Between 800 and 849

At Cummins, we empower everyone to grow their careers through meaningful work, building inclusive and equitable teams, coaching, development and opportunities to make a difference. Across our entire organization, you'll find engineers, developers, and technicians who are innovating, designing, testing, and building. You'll also find accountants, marketers, as well as manufacturing, quality and supply chain specialists who are working with technology that's just as innovative and advanced. From your first day at Cummins, we’re focused on understanding your talents, current skills and future goals – and creating a plan to get you there. Your journey begins with planning your development and connecting to diverse experiences designed to spur innovation. From our internships to our senior leadership roles, we attract, hire and reward the best and brightest from around the world and look to them for new ideas and fresh perspectives. Learn more about #LifeAtCummins at cummins.com/careers.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/toyota.jpeg
Toyota 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
https://images.rankiteo.com/companyimages/cummins-inc.jpeg
Cummins Inc.
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
Toyota Motor Corporation
100%
Compliance Rate
0/4 Standards Verified
Cummins Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

Toyota Motor Corporation has 426.32% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Motor Vehicle Manufacturing Industry Average (This Year)

No incidents recorded for Cummins Inc. in 2025.

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

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

Incident History — Cummins Inc. (X = Date, Y = Severity)

Cummins Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/toyota.jpeg
Toyota Motor Corporation
Incidents

Date Detected: 10/2025
Type:Cyber Attack
Attack Vector: Exploitation of Salesforce Customer Instances, OAuth Abuse, Third-Party App Compromises (e.g., Salesloft’s Drift/Drift), VPN Masking for Exfiltration, Weak 2FA Enforcement
Motivation: Financial Gain (Ransom Extortion), Data Theft for Resale/Leverage, Public Disclosure Threats, Litigation Support as Pressure Tactic
Blog: Blog

Date Detected: 6/2025
Type:Ransomware
Attack Vector: Vulnerabilities within interconnected systems, Advanced reconnaissance techniques, Persistent access mechanisms
Motivation: Strategic objectives, Political objectives, Reputation damage
Blog: Blog

Date Detected: 06/2023
Type:Data Leak
Attack Vector: Improperly setup cloud services
Blog: Blog
https://images.rankiteo.com/companyimages/cummins-inc.jpeg
Cummins Inc.
Incidents

No Incident

FAQ

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

Toyota Motor Corporation company has historically faced a number of disclosed cyber incidents, whereas Cummins Inc. company has not reported any.

In the current year, Toyota Motor Corporation company has reported more cyber incidents than Cummins Inc. company.

Toyota Motor Corporation company has confirmed experiencing a ransomware attack, while Cummins Inc. company has not reported such incidents publicly.

Toyota Motor Corporation company has disclosed at least one data breach, while the other Cummins Inc. company has not reported such incidents publicly.

Toyota Motor Corporation company has reported targeted cyberattacks, while Cummins Inc. company has not reported such incidents publicly.

Neither Toyota Motor Corporation company nor Cummins Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Toyota Motor Corporation nor Cummins Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Cummins Inc. company has more subsidiaries worldwide compared to Toyota Motor Corporation company.

Cummins Inc. company employs more people globally than Toyota Motor Corporation company, reflecting its scale as a Motor Vehicle Manufacturing.

Neither Toyota Motor Corporation nor Cummins Inc. holds SOC 2 Type 1 certification.

Neither Toyota Motor Corporation nor Cummins Inc. holds SOC 2 Type 2 certification.

Neither Toyota Motor Corporation nor Cummins Inc. holds ISO 27001 certification.

Neither Toyota Motor Corporation nor Cummins Inc. holds PCI DSS certification.

Neither Toyota Motor Corporation nor Cummins Inc. holds HIPAA certification.

Neither Toyota Motor Corporation nor Cummins Inc. 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