Comparison Overview

Jack in the Box

VS

LongHorn Steakhouse

Jack in the Box

9357 Spectrum Center Blvd, San Diego, California, US, 92123
Last Update: 2026-04-02
Between 750 and 799

Jack in the Box has always been the place for those who live outside the box. Where you can try new things and order what you want when you want it. Now, let’s get to the facts! Did you know Jack in the Box was founded on February 21, 1951, by a businessman named Robert O. Peterson in San Diego, California? Yeah, you probably did. Did you know Jack in the Box pioneered a number of firsts in the quick-serve industry, including menu items that are now staples on most fast-food menu boards, like the breakfast sandwich and portable salads. Sure. Did you know Jack in the Box has over 2000 locations? Everyone knows that. Whatever the reason you came to Jack in the Box's LinkedIn page...welcome, we’re happy to have you here.

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

LongHorn Steakhouse

US
Last Update: 2026-04-01

With over 500+ restaurants across the United States, LongHorn Steakhouse has a passion for steak done the right way. Our legendary food sets us apart, but it’s our people who bring LongHorn to life. We strive to create a place where team members feel valued, listened to and appreciated. We offer offering best-in-class training and opportunities for career development. And, as part of the Darden family of restaurants, you'll have plenty of opportunities to lead, grow and develop to your full potential, while inspiring others to rise to theirs. We know that the right way is the only way, and we’re searching for people with a passion to help us become America’s favorite steakhouse, one guest, one community at a time. http://bit.ly/3rMyXtd #WeAreLongHorn

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/jack-in-the-box.jpeg
Jack in the Box
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/longhorn-steakhouse.jpeg
LongHorn Steakhouse
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
Jack in the Box
100%
Compliance Rate
0/4 Standards Verified
LongHorn Steakhouse
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for Jack in the Box in 2026.

Incidents vs Restaurants Industry Average (This Year)

No incidents recorded for LongHorn Steakhouse in 2026.

Incident History — Jack in the Box (X = Date, Y = Severity)

Jack in the Box cyber incidents detection timeline including parent company and subsidiaries

Incident History — LongHorn Steakhouse (X = Date, Y = Severity)

LongHorn Steakhouse cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jack-in-the-box.jpeg
Jack in the Box
Incidents

Date Detected: 1/2019
Type:Breach
Attack Vector: Phishing
Blog: Blog
https://images.rankiteo.com/companyimages/longhorn-steakhouse.jpeg
LongHorn Steakhouse
Incidents

Date Detected: 08/2018
Type:Breach
Blog: Blog

FAQ

LongHorn Steakhouse company demonstrates a stronger AI Cybersecurity Score compared to Jack in the Box company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Jack in the Box and LongHorn Steakhouse have experienced a similar number of publicly disclosed cyber incidents.

In the current year, LongHorn Steakhouse company and Jack in the Box company have not reported any cyber incidents.

Neither LongHorn Steakhouse company nor Jack in the Box company has reported experiencing a ransomware attack publicly.

Both LongHorn Steakhouse company and Jack in the Box company have disclosed experiencing at least one data breach.

Neither LongHorn Steakhouse company nor Jack in the Box company has reported experiencing targeted cyberattacks publicly.

Neither Jack in the Box company nor LongHorn Steakhouse company has reported experiencing or disclosing vulnerabilities publicly.

Neither Jack in the Box nor LongHorn Steakhouse holds any compliance certifications.

Neither company holds any compliance certifications.

LongHorn Steakhouse company has more subsidiaries worldwide compared to Jack in the Box company.

Jack in the Box company employs more people globally than LongHorn Steakhouse company, reflecting its scale as a Restaurants.

Neither Jack in the Box nor LongHorn Steakhouse holds SOC 2 Type 1 certification.

Neither Jack in the Box nor LongHorn Steakhouse holds SOC 2 Type 2 certification.

Neither Jack in the Box nor LongHorn Steakhouse holds ISO 27001 certification.

Neither Jack in the Box nor LongHorn Steakhouse holds PCI DSS certification.

Neither Jack in the Box nor LongHorn Steakhouse holds HIPAA certification.

Neither Jack in the Box nor LongHorn Steakhouse 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.

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
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.

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
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.

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
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.

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
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.

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