Comparison Overview

Rakuten

VS

DiDi

Rakuten

Rakuten Crimson House, 1-14-1 Tamagawa, Setagaya-ku, Tokyo, JP, 158-0094
Last Update: 2025-12-09
View Profile
Between 750 and 799
https://global.rakuten.com/corp/

Rakuten Group, Inc. (TSE: 4755) is a global technology leader in services that empower individuals, communities, businesses and society. Founded in Tokyo in 1997 as an online marketplace, Rakuten has expanded to offer services in e-commerce, fintech, digital content and communications to 2 billion members around the world. The Rakuten Group has more than 30,000 employees, and operations in 30 countries and regions. For more information visit https://global.rakuten.com/corp/.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 10,677
Subsidiaries: 24
12-month incidents
0
Known data breaches
2
Attack type number
1
View Profile

DiDi

-, Global, CN
Last Update: 2025-12-09
Between 750 and 799
http://www.didiglobal.com

DiDi Global Inc. is a leading mobility technology platform. It offers a wide range of app-based services across Asia Pacific, Latin America, and other global markets, including ride hailing, taxi hailing, designated driving, hitch and other forms of shared mobility as well as certain energy and vehicle services, food delivery, and intra-city freight services. DiDi provides car owners, drivers, and delivery partners with flexible work and income opportunities. It is committed to collaborating with policymakers, the taxi industry, the automobile industry, and the communities to solve the world’s transportation, environmental, and employment challenges through the use of AI technology and localized smart transportation innovations. DiDi strives to create better life experiences and greater social value, by building a safe, inclusive, and sustainable transportation and local services ecosystem for cities of the future.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 29,134
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rakuten.jpeg
Rakuten
—
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/didiglobal.jpeg
DiDi
—
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
Rakuten
100%
Compliance Rate
0/4 Standards Verified
DiDi
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Rakuten in 2025.

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for DiDi in 2025.

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

Rakuten cyber incidents detection timeline including parent company and subsidiaries

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

DiDi cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rakuten.jpeg
Rakuten
Incidents

Date Detected: 1/2021
Type:Breach
Attack Vector: Insider Wrongdoing
Blog: Blog

Date Detected: 4/2018
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/didiglobal.jpeg
DiDi
Incidents

Date Detected: 6/2021
Type:Breach
Motivation: Regulatory Enforcement, Data Privacy Compliance, Investor Protection
Blog: Blog

FAQ

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

Rakuten company has faced a higher number of disclosed cyber incidents historically compared to DiDi company.

In the current year, DiDi company and Rakuten company have not reported any cyber incidents.

Neither DiDi company nor Rakuten company has reported experiencing a ransomware attack publicly.

Both DiDi company and Rakuten company have disclosed experiencing at least one data breach.

Neither DiDi company nor Rakuten company has reported experiencing targeted cyberattacks publicly.

Neither Rakuten company nor DiDi company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rakuten nor DiDi holds any compliance certifications.

Neither company holds any compliance certifications.

Rakuten company has more subsidiaries worldwide compared to DiDi company.

DiDi company employs more people globally than Rakuten company, reflecting its scale as a Software Development.

Neither Rakuten nor DiDi holds SOC 2 Type 1 certification.

Neither Rakuten nor DiDi holds SOC 2 Type 2 certification.

Neither Rakuten nor DiDi holds ISO 27001 certification.

Neither Rakuten nor DiDi holds PCI DSS certification.

Neither Rakuten nor DiDi holds HIPAA certification.

Neither Rakuten nor DiDi holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
References
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/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
References
Description

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
References
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Published
Date
2025-12-14
Updated
Date
2025-12-14
Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
References