Comparison Overview

Frito-Lay

VS

Kerry

Frito-Lay

7701 Legacy Dr, Plano, Texas, US, 75024
Last Update: 2025-11-20
Between 750 and 799

We believe every consumer should have access to their favorite snack, everywhere. We own the manufacturing process from seed to shelf and actively invest in technology to automate key steps of the process. This helps us be more agile in what we need to make, who we need to make it for, and how we can best deliver it to snack lovers from coast to coast.

NAICS: 722
NAICS Definition: Food Services and Drinking Places
Employees: 15,749
Subsidiaries: 6
12-month incidents
0
Known data breaches
0
Attack type number
0

Kerry

Naas, IE
Last Update: 2025-11-21
Between 750 and 799

Every day, millions of people throughout the world consume foods and beverages containing Kerry’s taste and nutrition solutions. We are committed to making the world of food and beverage better for everyone, and dedicated to our Purpose, Inspiring Food, Nourishing Life. At Kerry, we are proud to provide our customers – some of the world’s best-known food, beverage and pharma brands – with the expertise, insights and know-how they need to deliver products that people enjoy and feel better about consuming. Kerry is a company rich in heritage and resources. Over the past five decades, our focus on changing lifestyles, the globalisation of food tastes and ever-evolving consumer needs has brought us to a market-leading global position. Today, we are firmly established as a world leader in the food, beverage and pharma industries, with 22,000+ staff and 150+ innovation and manufacturing centres across 30+ countries. Learn more about Kerry: www.kerry.com

NAICS: 722
NAICS Definition: Food Services and Drinking Places
Employees: 16,483
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/frito-lay.jpeg
Frito-Lay
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/kerry.jpeg
Kerry
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
Frito-Lay
100%
Compliance Rate
0/4 Standards Verified
Kerry
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for Frito-Lay in 2025.

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for Kerry in 2025.

Incident History — Frito-Lay (X = Date, Y = Severity)

Frito-Lay cyber incidents detection timeline including parent company and subsidiaries

Incident History — Kerry (X = Date, Y = Severity)

Kerry cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/frito-lay.jpeg
Frito-Lay
Incidents

No Incident

https://images.rankiteo.com/companyimages/kerry.jpeg
Kerry
Incidents

No Incident

FAQ

Kerry company demonstrates a stronger AI Cybersecurity Score compared to Frito-Lay company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Kerry company has disclosed a higher number of cyber incidents compared to Frito-Lay company.

In the current year, Kerry company and Frito-Lay company have not reported any cyber incidents.

Neither Kerry company nor Frito-Lay company has reported experiencing a ransomware attack publicly.

Neither Kerry company nor Frito-Lay company has reported experiencing a data breach publicly.

Neither Kerry company nor Frito-Lay company has reported experiencing targeted cyberattacks publicly.

Neither Frito-Lay company nor Kerry company has reported experiencing or disclosing vulnerabilities publicly.

Neither Frito-Lay nor Kerry holds any compliance certifications.

Neither company holds any compliance certifications.

Frito-Lay company has more subsidiaries worldwide compared to Kerry company.

Kerry company employs more people globally than Frito-Lay company, reflecting its scale as a Food and Beverage Services.

Neither Frito-Lay nor Kerry holds SOC 2 Type 1 certification.

Neither Frito-Lay nor Kerry holds SOC 2 Type 2 certification.

Neither Frito-Lay nor Kerry holds ISO 27001 certification.

Neither Frito-Lay nor Kerry holds PCI DSS certification.

Neither Frito-Lay nor Kerry holds HIPAA certification.

Neither Frito-Lay nor Kerry 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