Comparison Overview

Waffle House, Inc.

VS

TGI Fridays

Waffle House, Inc.

5986 Financial Dr NW, None, Norcross, Georgia, US, 30071
Last Update: 2025-11-20
Between 750 and 799

Waffle House has been serving Good Food Fast® since 1955. We started in one restaurant serving Avondale Estates, GA, and then grew into a national brand with more than 1,900 restaurants in 25 states providing career paths to 40,000 + employees. The love and devotion of our customer base helped build the Waffle House Brand into a name recognized around the world. Our mission is to serve great food and care for people on both sides of the counter, Customers and Associates alike. Whether it’s early morning, late night, or anywhere in between, we’re always open. Thanks to our culture of promoting from within, we provide lasting career opportunities that are unmatched within this industry. Whether you’re working alongside us in Restaurant Operations or on our Corporate Support Team, you can help us continue the mission our founders began in 1955. Learn more about Waffle House by visiting our website at www.wafflehouse.com/careers and following us on LinkedIn.

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

TGI Fridays

19111 North Dallas Parkway, Dallas, Texas, 75287, US
Last Update: 2025-11-22
Between 750 and 799

In 1965, TGI Fridays opened its first location in New York City. Today, there are 890 restaurants in 60 countries offering high quality, authentic American food and legendary drinks, bringing together all people from all places. The freeing and liberating spirit of "Friday"​ combined with our belief that all are welcome is our founding premise. We are The People of All Stripes. For more information, visit www.Fridays.com or follow us on Twitter at @TGIFridays.

NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 13,191
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/waffle-house.jpeg
Waffle House, Inc.
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/tgi-fridays.jpeg
TGI Fridays
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
Waffle House, Inc.
100%
Compliance Rate
0/4 Standards Verified
TGI Fridays
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Waffle House, Inc. in 2025.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for TGI Fridays in 2025.

Incident History — Waffle House, Inc. (X = Date, Y = Severity)

Waffle House, Inc. cyber incidents detection timeline including parent company and subsidiaries

Incident History — TGI Fridays (X = Date, Y = Severity)

TGI Fridays cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/waffle-house.jpeg
Waffle House, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/tgi-fridays.jpeg
TGI Fridays
Incidents

No Incident

FAQ

Waffle House, Inc. company demonstrates a stronger AI Cybersecurity Score compared to TGI Fridays company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, TGI Fridays company has disclosed a higher number of cyber incidents compared to Waffle House, Inc. company.

In the current year, TGI Fridays company and Waffle House, Inc. company have not reported any cyber incidents.

Neither TGI Fridays company nor Waffle House, Inc. company has reported experiencing a ransomware attack publicly.

Neither TGI Fridays company nor Waffle House, Inc. company has reported experiencing a data breach publicly.

Neither TGI Fridays company nor Waffle House, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Waffle House, Inc. company nor TGI Fridays company has reported experiencing or disclosing vulnerabilities publicly.

Neither Waffle House, Inc. nor TGI Fridays holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Waffle House, Inc. company nor TGI Fridays company has publicly disclosed detailed information about the number of their subsidiaries.

Waffle House, Inc. company employs more people globally than TGI Fridays company, reflecting its scale as a Restaurants.

Neither Waffle House, Inc. nor TGI Fridays holds SOC 2 Type 1 certification.

Neither Waffle House, Inc. nor TGI Fridays holds SOC 2 Type 2 certification.

Neither Waffle House, Inc. nor TGI Fridays holds ISO 27001 certification.

Neither Waffle House, Inc. nor TGI Fridays holds PCI DSS certification.

Neither Waffle House, Inc. nor TGI Fridays holds HIPAA certification.

Neither Waffle House, Inc. nor TGI Fridays 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