Comparison Overview

Popeyes Louisiana Kitchen

VS

In-N-Out Burger

Popeyes Louisiana Kitchen

5707 Blue Lagoon Dr, Miami, Florida, US, 33126
Last Update: 2026-04-02
View Profile
Between 700 and 749
http://www.popeyes.com

Founded in New Orleans in 1972, POPEYES® has more than 45 years of history and culinary tradition. Popeyes distinguishes itself with a unique New Orleans-style menu featuring spicy chicken, chicken tenders, fried shrimp, and other regional items. The chain's passion for its Louisiana heritage and flavorful authentic food has allowed Popeyes to become one of the world's largest chicken quick-service restaurants with over 3,600 restaurants in the U.S. and around the world.

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

In-N-Out Burger

4199 Campus Drive, Irvine, 92612, US
Last Update: 2026-04-01
Between 750 and 799
http://www.in-n-out.com

In-N-Out Burger was founded in 1948 by Harry and Esther Snyder in Baldwin Park, California, and remains privately owned and operated. Under the direction of the Snyder family, the company has opened restaurants throughout California, Nevada, Arizona, Utah, Texas, Oregon, Colorado, and Idaho. In-N-Out Burger’s menu has remained the same since 1948, and we have maintained a simple philosophy – serve only the highest quality product, prepare it in a clean and sparkling environment, and serve it in a warm and friendly manner. We have built a reputation for fresh, made-to-order foods prepared and served by friendly, well trained Associates.

NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 13,366
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/popeyes-louisiana-kitchen.jpeg
Popeyes Louisiana Kitchen
—
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/in-n-out-burger.jpeg
In-N-Out Burger
—
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
Popeyes Louisiana Kitchen
100%
Compliance Rate
0/4 Standards Verified
In-N-Out Burger
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Popeyes Louisiana Kitchen in 2026.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for In-N-Out Burger in 2026.

Incident History — Popeyes Louisiana Kitchen (X = Date, Y = Severity)

Popeyes Louisiana Kitchen cyber incidents detection timeline including parent company and subsidiaries

Incident History — In-N-Out Burger (X = Date, Y = Severity)

In-N-Out Burger cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/popeyes-louisiana-kitchen.jpeg
Popeyes Louisiana Kitchen
Incidents

Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Weak Default Credentials, Insecure Direct Object Reference (IDOR)
Blog: Blog

Date Detected: 9/2024
Type:Breach
Attack Vector: Third-Party Vendor Compromise
Blog: Blog
https://images.rankiteo.com/companyimages/in-n-out-burger.jpeg
In-N-Out Burger
Incidents

No Incident

FAQ

In-N-Out Burger company demonstrates a stronger AI Cybersecurity Score compared to Popeyes Louisiana Kitchen company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Popeyes Louisiana Kitchen company has historically faced a number of disclosed cyber incidents, whereas In-N-Out Burger company has not reported any.

In the current year, In-N-Out Burger company and Popeyes Louisiana Kitchen company have not reported any cyber incidents.

Neither In-N-Out Burger company nor Popeyes Louisiana Kitchen company has reported experiencing a ransomware attack publicly.

Popeyes Louisiana Kitchen company has disclosed at least one data breach, while the other In-N-Out Burger company has not reported such incidents publicly.

Neither In-N-Out Burger company nor Popeyes Louisiana Kitchen company has reported experiencing targeted cyberattacks publicly.

Popeyes Louisiana Kitchen company has disclosed at least one vulnerability, while In-N-Out Burger company has not reported such incidents publicly.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Popeyes Louisiana Kitchen company nor In-N-Out Burger company has publicly disclosed detailed information about the number of their subsidiaries.

Popeyes Louisiana Kitchen company employs more people globally than In-N-Out Burger company, reflecting its scale as a Restaurants.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds SOC 2 Type 1 certification.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds SOC 2 Type 2 certification.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds ISO 27001 certification.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds PCI DSS certification.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds HIPAA certification.

Neither Popeyes Louisiana Kitchen nor In-N-Out Burger holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A vulnerability was found in Nothings stb up to 1.26. Impacted is the function stbtt_InitFont_internal in the library stb_truetype.h of the component TTF File Handler. Performing a manipulation results in out-of-bounds read. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:N/A:P
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/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
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read in VS6ComFile!get_macro_mem_COM. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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
References
Description

V-SFT versions 6.2.10.0 and prior contain a stack-based buffer overflow in VS6ComFile!CSaveData::_conv_AnimationItem. Opening a crafted V7 file may lead to arbitrary code execution on the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6MemInIF!set_temp_type_default. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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
References
Description

V-SFT versions 6.2.10.0 and prior contain an out-of-bounds read vulnerability in VS6ComFile!load_link_inf. Opening a crafted V7 file may lead to information disclosure from the affected product.

Published
Date
2026-04-01
Updated
Date
2026-04-01
Risk Information
cvss3
Base: 7.8
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
cvss4
Base: 8.4
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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
References