Comparison Overview

Chili's

VS

Papa Johns

Chili's

3000 Olympus Blvd, Dallas, Texas, 75019, US
Last Update: 2026-01-21
Between 750 and 799

Chili's opened as a fun Dallas burger joint with a loyalty to happy hour and blue jeans. We prided ourselves on our humble beginnings, following a devotion to great food, warm hospitality and community spirit. Today, with restaurants all over the world, we continue to cook up the best in casual fare, offering the same genuine service we did way back when. And, just as in 1975, we're committed to giving back to the communities that have helped us grow. Driven to perform? Insist on loving what you do? Then you have a lot in common with us. If you’re passionate about delivering hospitality to every guest, every day, please visit us online today at ChilisJobs.com.

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

Papa Johns

788 Circle 75 Pkwy SE, Atlanta, Georgia, US, 30339
Last Update: 2026-01-17
Between 750 and 799

Papa Johns seeks people who have an entrepreneurial spirit and share our philosophy for success. Hands-on training, a clean and safe work environment, quality business practices, advancement opportunities and meaningful work combine to produce not only the best pizza, but also the best team members! Better Opportunities. Better People! At Papa Johns we call ourselves team members instead of employees because we believe it is only through a strong team we can produce the best experience for our customers. Whether at our corporate campus, distribution centers, our restaurants, or located internationally; Papa Johns has a variety of positions for talented and passionate people. Papa Johns is an equal opportunity employer and provides excellent career opportunities for our entire team. Our company philosophies of promote from within and rewards based on performance are important elements of our company culture.

NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 28,758
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/chili's.jpeg
Chili's
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/papajohns.jpeg
Papa Johns
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
Chili's
100%
Compliance Rate
0/4 Standards Verified
Papa Johns
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Chili's in 2026.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Papa Johns in 2026.

Incident History — Chili's (X = Date, Y = Severity)

Chili's cyber incidents detection timeline including parent company and subsidiaries

Incident History — Papa Johns (X = Date, Y = Severity)

Papa Johns cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/chili's.jpeg
Chili's
Incidents

Date Detected: 5/2018
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/papajohns.jpeg
Papa Johns
Incidents

No Incident

FAQ

Chili's company demonstrates a stronger AI Cybersecurity Score compared to Papa Johns company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Chili's company has historically faced a number of disclosed cyber incidents, whereas Papa Johns company has not reported any.

In the current year, Papa Johns company and Chili's company have not reported any cyber incidents.

Neither Papa Johns company nor Chili's company has reported experiencing a ransomware attack publicly.

Chili's company has disclosed at least one data breach, while the other Papa Johns company has not reported such incidents publicly.

Neither Papa Johns company nor Chili's company has reported experiencing targeted cyberattacks publicly.

Neither Chili's company nor Papa Johns company has reported experiencing or disclosing vulnerabilities publicly.

Neither Chili's nor Papa Johns holds any compliance certifications.

Neither company holds any compliance certifications.

Chili's company has more subsidiaries worldwide compared to Papa Johns company.

Papa Johns company employs more people globally than Chili's company, reflecting its scale as a Restaurants.

Neither Chili's nor Papa Johns holds SOC 2 Type 1 certification.

Neither Chili's nor Papa Johns holds SOC 2 Type 2 certification.

Neither Chili's nor Papa Johns holds ISO 27001 certification.

Neither Chili's nor Papa Johns holds PCI DSS certification.

Neither Chili's nor Papa Johns holds HIPAA certification.

Neither Chili's nor Papa Johns holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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