Comparison Overview

Jimmy John's

VS

Papa Johns

Jimmy John's

3 Glenlake Pkwy NE, None, Sandy Springs, Georgia, US, 30328
Last Update: 2025-12-25
Between 750 and 799

THE SANDWICH OF SANDWICHES℠ At Jimmy John's, we don't make sandwiches. We make The Sandwich of Sandwiches℠. We use fresh vegetables because we don't hate salads, we just feel bad for them. We hand-slice our provolone cheese and meats in-house every day, because packaged pre-sliced meats doesn't have the same ring to it. And we bake bread all day, every day because stale bread isn't bread, it's... croutons. The flavors of fresh-veggies, combined with hand-sliced meats and fresh-baked bread is what makes a Jimmy John's sandwich The Sandwich of Sandwiches℠. For more information, visit jimmyjohns.com and InspireBrands.com. For careers, visit our careers site: careers.jimmyjohns.com Connect with us on social media: instagram.com/jimmyjohns facebook.com/jimmyjohns twitter.com/jimmyjohns tiktok.com/@jimmyjohns pinterest.com/jimmyjohns www.youtube.com/user/jimmyjohns www.InspireBrands.com This profile is for Jimmy John's Headquarters. Each Jimmy John's is independently owned and operated under a franchise agreement with Jimmy John's Franchise, LLC, franchisor of the JIMMY JOHN'S system. Any questions regarding employment must be directed to the franchise owner/operator. Jimmy John’s Franchise, LLC does not have access to franchisees’ employment records or specific rules for employment as defined by the franchisees.

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

Papa Johns

788 Circle 75 Pkwy SE, Atlanta, Georgia, 30339, US
Last Update: 2025-12-20
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: 25,896
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/jimmy-john's.jpeg
Jimmy John'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/papa-johns-international.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
Jimmy John'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 Jimmy John's in 2025.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Papa Johns in 2025.

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

Jimmy John'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/jimmy-john's.jpeg
Jimmy John's
Incidents

Date Detected: 6/2014
Type:Cyber Attack
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/papa-johns-international.jpeg
Papa Johns
Incidents

No Incident

FAQ

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

Jimmy John'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 Jimmy John's company have not reported any cyber incidents.

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

Neither Papa Johns company nor Jimmy John's company has reported experiencing a data breach publicly.

Jimmy John's company has reported targeted cyberattacks, while Papa Johns company has not reported such incidents publicly.

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

Neither Jimmy John's nor Papa Johns holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Jimmy John's company nor Papa Johns company has publicly disclosed detailed information about the number of their subsidiaries.

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

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

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

Neither Jimmy John's nor Papa Johns holds ISO 27001 certification.

Neither Jimmy John's nor Papa Johns holds PCI DSS certification.

Neither Jimmy John's nor Papa Johns holds HIPAA certification.

Neither Jimmy John's nor Papa Johns holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

httparty is an API tool. In versions 0.23.2 and prior, httparty is vulnerable to SSRF. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers. This issue has been patched via commit 0529bcd.

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

5ire is a cross-platform desktop artificial intelligence assistant and model context protocol client. In versions 0.15.2 and prior, an RCE vulnerability exists in useMarkdown.ts, where the markdown-it-mermaid plugin is initialized with securityLevel: 'loose'. This configuration explicitly permits the rendering of HTML tags within Mermaid diagram nodes. This issue has not been patched at time of publication.

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

continuwuity is a Matrix homeserver written in Rust. Prior to version 0.5.0, this vulnerability allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. This issue has been patched in version 0.5.0. A workaround for this issue involves blocking access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint using the reverse proxy.

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

LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3

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

LangChain is a framework for building agents and LLM-powered applications. Prior to versions 0.3.81 and 1.2.5, a serialization injection vulnerability exists in LangChain's dumps() and dumpd() functions. The functions do not escape dictionaries with 'lc' keys when serializing free-form dictionaries. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in versions 0.3.81 and 1.2.5.

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