Comparison Overview

Agoda

VS

Booking.com

Agoda

20 Cecil Street, #1401, Singapore, Singapore, 049705, SG
Last Update: 2025-11-27
Between 750 and 799

At Agoda, we bridge the world through travel. We aim to make it easy and rewarding for more travelers to explore and experience the amazing world we live in. We do so by enabling more people to see the world for less – with our best-value deals across our 4,700,000+ hotels and holiday properties, 130,000+ flight routes, 300,000+ activities, and more. Agoda was founded in 2005 in Thailand by two lifelong friends with a shared passion for travel. Today, Agoda is part of Booking Holdings [BKNG], and we have more than 7,000 employees from 90 nationalities in offices across Asia Pacific, the Middle East, Europe, and the Americas. In every department – from engineering to customer support – you’ll find that data and technology are at the heart of our culture. There’s never a boring day at Agoda as we aim to make travel hassle-free for everyone. If you’re ready to begin your best journey with us and help us build travel for the world, join us. For properties seeking partnership with Agoda, visit https://connect.agoda.com

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

Booking.com

Oosterdokskade 163, None, Amsterdam, North Holland, NL, 1011 DL
Last Update: 2025-11-25
Between 750 and 799

A career at Booking.com is all about the journey, helping you explore new challenges in a place where you can be your best self. With plenty of exciting twists, turns and opportunities along the way. We’ve always been pioneers, on a mission to shape the future of travel through cutting edge technology, to make it easier for everyone to enjoy amazing experiences wherever they go. Under a desert sky, or in the heart of a bustling city. Discovering the perfect hideaway, or the perfect paella. When you join us, you’ll be part of a community where taking a different path and trying something new is celebrated and supported. And where making a difference counts. We’re determined to make the world of travel more sustainable, more accessible, and more inclusive, to create a positive impact on a global scale. That’s why we’re always looking for people who search for better solutions, the ones eager to stray off the beaten path to find new ways of doing things. Because at Booking.com it’s more than a job, it’s a journey we’re on together.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 15,885
Subsidiaries: 11
12-month incidents
3
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/agoda.jpeg
Agoda
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/booking.com.jpeg
Booking.com
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
Agoda
100%
Compliance Rate
0/4 Standards Verified
Booking.com
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Agoda in 2025.

Incidents vs Software Development Industry Average (This Year)

Booking.com has 581.82% more incidents than the average of same-industry companies with at least one recorded incident.

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

Agoda cyber incidents detection timeline including parent company and subsidiaries

Incident History — Booking.com (X = Date, Y = Severity)

Booking.com cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/agoda.jpeg
Agoda
Incidents

Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: Mass-phishing, Infostealer trojans
Motivation: Financial gain
Blog: Blog

Date Detected: 4/2025
Type:Cyber Attack
Attack Vector: compromised email accounts, phishing links, fake reCAPTCHA challenge, malware download (PureRAT), personalized WhatsApp messages, fake Booking/Expedia websites
Motivation: financial gain, data theft, fraudulent transactions
Blog: Blog

Date Detected: 2/2025
Type:Cyber Attack
Attack Vector: malicious domain registration, social engineering, phishing emails/websites
Motivation: financial gain, theft of payment details
Blog: Blog
https://images.rankiteo.com/companyimages/booking.com.jpeg
Booking.com
Incidents

Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: Mass-phishing, Infostealer trojans
Motivation: Financial gain
Blog: Blog

Date Detected: 4/2025
Type:Cyber Attack
Attack Vector: compromised email accounts, phishing links, fake reCAPTCHA challenge, malware download (PureRAT), personalized WhatsApp messages, fake Booking/Expedia websites
Motivation: financial gain, data theft, fraudulent transactions
Blog: Blog

Date Detected: 2/2025
Type:Cyber Attack
Attack Vector: malicious domain registration, social engineering, phishing emails/websites
Motivation: financial gain, theft of payment details
Blog: Blog

FAQ

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

Agoda and Booking.com have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Booking.com and Agoda have reported a similar number of cyber incidents.

Neither Booking.com company nor Agoda company has reported experiencing a ransomware attack publicly.

Neither Booking.com company nor Agoda company has reported experiencing a data breach publicly.

Both Booking.com company and Agoda company have reported experiencing targeted cyberattacks.

Neither Agoda company nor Booking.com company has reported experiencing or disclosing vulnerabilities publicly.

Neither Agoda nor Booking.com holds any compliance certifications.

Neither company holds any compliance certifications.

Both Booking.com company and Agoda company have a similar number of subsidiaries worldwide.

Booking.com company employs more people globally than Agoda company, reflecting its scale as a Software Development.

Neither Agoda nor Booking.com holds SOC 2 Type 1 certification.

Neither Agoda nor Booking.com holds SOC 2 Type 2 certification.

Neither Agoda nor Booking.com holds ISO 27001 certification.

Neither Agoda nor Booking.com holds PCI DSS certification.

Neither Agoda nor Booking.com holds HIPAA certification.

Neither Agoda nor Booking.com 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