Comparison Overview

Bloomin'​ Brands, Inc.

VS

Jimmy John's

Bloomin'​ Brands, Inc.

2202 N West Shore Blvd, None, Tampa, Florida, US, 33607
Last Update: 2025-11-27
Between 750 and 799

Since the first Outback Steakhouse opened, our family of brands has expanded to include Carrabba's Italian Grill, Bonefish Grill, and Fleming's Prime Steakhouse & Wine Bar. Together, these unique, Founder-inspired restaurants make up Bloomin' Brands, Inc. Today, we are one of the world's largest casual dining companies with approximately 81,000 Team Members and more than 1,450 restaurants worldwide. Bloomin’ Brands, Inc. is a company of restaurants, not a restaurant company. Our brands were founded by people who have a genuine passion for food and a desire to share hospitality with others. Our focus on quality extends beyond the food and service we provide to our guests – Our People are what set us apart and they are at the center of everything we do!

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

Jimmy John's

3 Glenlake Pkwy NE, None, Sandy Springs, Georgia, US, 30328
Last Update: 2025-11-21
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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bloomin'​-brands-inc.jpeg
Bloomin'​ Brands, 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/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
Compliance Summary
Bloomin'​ Brands, Inc.
100%
Compliance Rate
0/4 Standards Verified
Jimmy John's
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Bloomin'​ Brands, Inc. in 2025.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Jimmy John's in 2025.

Incident History — Bloomin'​ Brands, Inc. (X = Date, Y = Severity)

Bloomin'​ Brands, Inc. cyber incidents detection timeline including parent company and subsidiaries

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

Jimmy John's cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bloomin'​-brands-inc.jpeg
Bloomin'​ Brands, Inc.
Incidents

No Incident

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

FAQ

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

Jimmy John's company has historically faced a number of disclosed cyber incidents, whereas Bloomin'​ Brands, Inc. company has not reported any.

In the current year, Jimmy John's company and Bloomin'​ Brands, Inc. company have not reported any cyber incidents.

Neither Jimmy John's company nor Bloomin'​ Brands, Inc. company has reported experiencing a ransomware attack publicly.

Neither Jimmy John's company nor Bloomin'​ Brands, Inc. company has reported experiencing a data breach publicly.

Jimmy John's company has reported targeted cyberattacks, while Bloomin'​ Brands, Inc. company has not reported such incidents publicly.

Neither Bloomin'​ Brands, Inc. company nor Jimmy John's company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bloomin'​ Brands, Inc. company nor Jimmy John's company has publicly disclosed detailed information about the number of their subsidiaries.

Jimmy John's company employs more people globally than Bloomin'​ Brands, Inc. company, reflecting its scale as a Restaurants.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds SOC 2 Type 1 certification.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds SOC 2 Type 2 certification.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds ISO 27001 certification.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds PCI DSS certification.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's holds HIPAA certification.

Neither Bloomin'​ Brands, Inc. nor Jimmy John's 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