Comparison Overview

Five Guys Enterprises

VS

Yum China

Five Guys Enterprises

1940 Duke St, Alexandria, Virginia, US, 22314
Last Update: 2025-11-20

History: *1986: The first Five Guys location opens in Arlington, VA. *1986 - 2001: Five Guys opens five locations around the DC metro-area and perfected their business of making burgers… and starts to build a cult-like following. * 2002: Five Guys decides DC metro-area residents shouldn't be the only ones to experience their burgers and start to franchise in Virginia and Maryland. * 2003: Five Guys sells out of franchise territory within 18 months and starts to open the rest of the country for franchise rights. * 2003 - 2012: Five Guys expands to over 1,000 locations in the U.S. and Canada. * In July 2013, Five Guys opens the first location outside of North America in London, England. * Our International HQ in Amsterdam, NL opened in 2016. * Today, we have more than 1,900 locations open in North America, Canada, UK, Middle East, Europe, APAC and growing.

NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 10,839
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Yum China

No. 20, Tianyaoqiao Road Shanghai, Shanghai 200030, CN
Last Update: 2025-11-26
Between 800 and 849

Yum China Holdings, Inc. (the “Company” or “Yum China”) (NYSE: YUMC and HKEX: 9987) is China’s largest restaurant company with a mission to make every life taste beautiful. From a single restaurant in 1987, the Company now operates over 14,000 restaurants in over 1,900 cities and towns spanning every province and autonomous region across mainland China. In 2022, Yum China was selected as a member of both Dow Jones Sustainability Indices (DJSI): World Index and Emerging Market Index for the third consecutive year. In 2023, Yum China was named to the Bloomberg Gender-Equality Index and was certified as a Top Employer in China by the Top Employers Institute, both for the fifth consecutive year. Yum China became an independent publicly traded company on November 1, 2016 on the NYSE. The Company was secondary-listed on the HKEX on September 10, 2020. On October 24, 2022, the Company became dual primary listed on both the HKEX and the NYSE.

NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/five-guys-enterprises.jpeg
Five Guys Enterprises
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/yum-china.jpeg
Yum China
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
Five Guys Enterprises
100%
Compliance Rate
0/4 Standards Verified
Yum China
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Five Guys Enterprises in 2025.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Yum China in 2025.

Incident History — Five Guys Enterprises (X = Date, Y = Severity)

Five Guys Enterprises cyber incidents detection timeline including parent company and subsidiaries

Incident History — Yum China (X = Date, Y = Severity)

Yum China cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/five-guys-enterprises.jpeg
Five Guys Enterprises
Incidents

Date Detected: 12/2022
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/yum-china.jpeg
Yum China
Incidents

No Incident

FAQ

Yum China company demonstrates a stronger AI Cybersecurity Score compared to Five Guys Enterprises company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Five Guys Enterprises company has historically faced a number of disclosed cyber incidents, whereas Yum China company has not reported any.

In the current year, Yum China company and Five Guys Enterprises company have not reported any cyber incidents.

Neither Yum China company nor Five Guys Enterprises company has reported experiencing a ransomware attack publicly.

Neither Yum China company nor Five Guys Enterprises company has reported experiencing a data breach publicly.

Neither Yum China company nor Five Guys Enterprises company has reported experiencing targeted cyberattacks publicly.

Neither Five Guys Enterprises company nor Yum China company has reported experiencing or disclosing vulnerabilities publicly.

Neither Five Guys Enterprises nor Yum China holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Five Guys Enterprises company nor Yum China company has publicly disclosed detailed information about the number of their subsidiaries.

Five Guys Enterprises company employs more people globally than Yum China company, reflecting its scale as a Restaurants.

Neither Five Guys Enterprises nor Yum China holds SOC 2 Type 1 certification.

Neither Five Guys Enterprises nor Yum China holds SOC 2 Type 2 certification.

Neither Five Guys Enterprises nor Yum China holds ISO 27001 certification.

Neither Five Guys Enterprises nor Yum China holds PCI DSS certification.

Neither Five Guys Enterprises nor Yum China holds HIPAA certification.

Neither Five Guys Enterprises nor Yum China 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