Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

BYDBYD
VS
Tata MotorsTata Motors
BYD

BYD

No.3009, BYD Road, Pingshan, Shenzhen, 518118, CN

Last Update: 04/08/2026

View Profile
Between 800 and 849
http://www.bydglobal.com
821/1000Good

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, ce...

NAICS:3361
NAICS Definition:Motor Vehicle Manufacturing
Employees:17,661
Subsidiaries:0
12-month incidents
0
Known data breaches
0
Attack type number
0
Tata Motors

Tata Motors

Bypass Road, Pune, 411046, IN

Last Update: 03/04/2026

View Profile
Between 650 and 699
http://www.tatamotors.com
657/1000Weak

At the forefront of shaping mobility for over eight decades, driven by a legacy of innovation and an unwavering commitment to excellence. We fuse next-generation technologies with operational precision and continuous value creation — across every vehicle and process. B...

NAICS:3361
NAICS Definition:Motor Vehicle Manufacturing
Employees:74,662
Subsidiaries:67
12-month incidents
0
Known data breaches
1
Attack type number
2

Compliance Ranges Comparison

Based On Specific Ai Models Category
BYD

BYD

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Tata Motors

Tata Motors

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)

No incidents recorded for BYD in 2026.

Incidents

Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)

No incidents recorded for Tata Motors in 2026.

Incidents

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

BYD cyber incidents detection timeline including parent company and subsidiaries.

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Incident History - Tata Motors (X = Date, Y = Severity)

Tata Motors cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
BYD

BYD

Incidents
No explicit notable incidents reported.
Tata Motors

Tata Motors

Incidents
🔒 Incident : Cyber Attack
TAT0662106111725
🔒 Incident : Breach
TAT2032920103125

FAQ

Between BYD company and Tata Motors company, which one has the best AI Cybersecurity Score ?
Between BYD company and Tata Motors company, which one has experienced more cyber incidents in the past ?
Between BYD company and Tata Motors company, which one has experienced more cyber incidents this year ?
Between BYD company and Tata Motors company, which one has experienced at least one ransomware attack ?
Between BYD company and Tata Motors company, which one has experienced at least one data breach ?
Between BYD company and Tata Motors company, which one has experienced at least one targeted cyberattack ?
Between BYD company and Tata Motors company, which one has experienced at least one vulnerability ?
Between BYD company and Tata Motors company, which one holds the most compliance certifications ?
Between BYD company and Tata Motors company, which one holds the fewest compliance certifications ?
Between BYD company and Tata Motors company, which one has the most subsidiaries ?
Between BYD company and Tata Motors company, which one has the largest number of employees ?
Between BYD and Tata Motors, which company holds both SOC 2 Type 1 certifications ?
Between BYD and Tata Motors, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - BYD or Tata Motors ?
Which company is PCI DSS compliant - BYD or Tata Motors ?
Between BYD and Tata Motors, which company complies with HIPAA regulations for healthcare data ?
Between BYD and Tata Motors, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-74250
SUMMARY

In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 6.3)
CVSS3
Base Score: 6.3
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
IMPACT SCORE
4
EXPLOITABILITY
1.8
CVE-2026-74247
SUMMARY

A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 4.2)
CVSS3
Base Score: 4.2
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
IMPACT SCORE
2.5
EXPLOITABILITY
1.6
CVE-2026-74245
SUMMARY

A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 5.9)
CVSS3
Base Score: 5.9
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
2.2
CVE-2026-74244
SUMMARY

A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 5.9)
CVSS3
Base Score: 5.9
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
2.2
CVE-2026-74243
SUMMARY

A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
IMPACT SCORE
2.5
EXPLOITABILITY
3.9