Comparison Overview

Rakuten

VS

DoorDash

Rakuten

Rakuten Crimson House, 1-14-1 Tamagawa, Setagaya-ku, Tokyo, JP, 158-0094
Last Update: 2025-12-09

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

DoorDash

San Francisco, California, US
Last Update: 2025-12-11

At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and we are looking for team members who can help us go from a company that is known for delivering food to a company that people turn to for any and all goods. DoorDash is growing rapidly and changing constantly, which gives our team members the opportunity to share their unique perspectives, solve new challenges, and own their careers. Our leaders seek the truth and welcome big, hairy, audacious questions. We are grounded in our company values, and we make intentional decisions that are both logical and display empathy for our range of users—from Dashers to Merchants to Customers.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 74,124
Subsidiaries: 2
12-month incidents
3
Known data breaches
9
Attack type number
2

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/doordash.jpeg
DoorDash
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
DoorDash
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)

DoorDash has 417.24% more incidents than the average of same-industry companies with at least one recorded incident.

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

Rakuten cyber incidents detection timeline including parent company and subsidiaries

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

DoorDash 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/doordash.jpeg
DoorDash
Incidents

Date Detected: 11/2025
Type:Breach
Attack Vector: Third-Party Vendor Compromise, Credential Theft, Social Engineering
Motivation: Data Theft, Potential Fraud Enablement
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering (Employee Targeted)
Blog: Blog

Date Detected: 10/2025
Type:Breach
Attack Vector: Social Engineering, Phishing (Spear Phishing/Vishing), Compromised Credentials
Motivation: Data Theft for Follow-on Attacks (e.g., Spear Phishing, Vishing), Potential Financial Gain via Stolen Data
Blog: Blog

FAQ

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

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

In the current year, DoorDash company has reported more cyber incidents than Rakuten company.

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

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

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

DoorDash company has disclosed at least one vulnerability, while Rakuten company has not reported such incidents publicly.

Neither Rakuten nor DoorDash holds any compliance certifications.

Neither company holds any compliance certifications.

Rakuten company has more subsidiaries worldwide compared to DoorDash company.

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

Neither Rakuten nor DoorDash holds SOC 2 Type 1 certification.

Neither Rakuten nor DoorDash holds SOC 2 Type 2 certification.

Neither Rakuten nor DoorDash holds ISO 27001 certification.

Neither Rakuten nor DoorDash holds PCI DSS certification.

Neither Rakuten nor DoorDash holds HIPAA certification.

Neither Rakuten nor DoorDash holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N