Comparison Overview

DiDi

VS

Airbnb

DiDi

-, Global, CN
Last Update: 2025-11-24
Between 750 and 799

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

Airbnb

888 Brannan Street, San Francisco, CA, US, 94103
Last Update: 2025-11-27
Between 800 and 849

Airbnb was born in 2007 when two hosts welcomed three guests to their San Francisco home, and has since grown to over 5 million hosts who have welcomed over 2 billion guest arrivals in almost every country across the globe. Every day, hosts offer unique stays, experiences and services that make it possible for guests to connect with communities in a more authentic way.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

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

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for DiDi in 2025.

Incidents vs Software Development Industry Average (This Year)

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

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

DiDi cyber incidents detection timeline including parent company and subsidiaries

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

Airbnb cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

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
https://images.rankiteo.com/companyimages/airbnb.jpeg
Airbnb
Incidents

Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: Phantom listing scam, Bait and switch scams, Fake positive reviews, Misleading property images, Delusive tactics
Motivation: Criminal intent or nefarious financial gain
Blog: Blog

FAQ

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

DiDi and Airbnb have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Airbnb company has reported more cyber incidents than DiDi company.

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

DiDi company has disclosed at least one data breach, while the other Airbnb company has not reported such incidents publicly.

Airbnb company has reported targeted cyberattacks, while DiDi company has not reported such incidents publicly.

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

Neither DiDi nor Airbnb holds any compliance certifications.

Neither company holds any compliance certifications.

Airbnb company has more subsidiaries worldwide compared to DiDi company.

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

Neither DiDi nor Airbnb holds SOC 2 Type 1 certification.

Neither DiDi nor Airbnb holds SOC 2 Type 2 certification.

Neither DiDi nor Airbnb holds ISO 27001 certification.

Neither DiDi nor Airbnb holds PCI DSS certification.

Neither DiDi nor Airbnb holds HIPAA certification.

Neither DiDi nor Airbnb 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