Comparison Overview

Kellogg Company

VS

SNEF

Kellogg Company

One Kellogg Square, Battle Creek, Michigan, 49017, US
Last Update: 2025-11-23
Between 800 and 849

At Kellanova, our vision is to be the world’s best performing snacks-led powerhouse, unleashing the full potential of our differentiated brands and our passionate people. Powered by our strategy to Differentiate, Drive & Deliver, we are a leading company in global snacking, international cereal and noodles, and North America frozen foods, with iconic, world-class brands and strong underlying growth momentum and profitability. Our purpose is to create better days and a place at the table for everyone through our trusted foods brands. As part of this purpose, we are committed to advancing sustainable & equitable access to food by creating Better Days for 4 billion people by the end of 2030.

NAICS: 30
NAICS Definition: Manufacturing
Employees: 15,288
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

SNEF

87, Avenue Ibrahim Ali Marseille, Provence-Alpes-Côte d'Azur 13015, FR
Last Update: 2025-11-21
Between 750 and 799

Group Snef is a French leader in the field of electrical installation and, more broadly, the management of finishing turnkey projects and operations. Group Snef operates in the fields of high- and low-voltage installations, industrial processes, HVAC and maintenance. Its services cover technical studies (design and implementation), installation, operation and maintenance. They are aimed at industry, tertiary sector, telecommunications operators, maritime sector, local government and public administrations. Founded in 1905 in Marseilles, where its headquarter is located, Group Snef achieved a turnover of € 857 million in 2010 and employs approximately 10,000 people worldwide. Group Snef operates throughout France via more than fifty agencies and more than thirty specialized subsidiaries. Group Snef operates worldwide, in particular in Western and Eastern Europe, Africa, the Middle East and Latin America.

NAICS: 339
NAICS Definition:
Employees: 10,001
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/kellogg-company.jpeg
Kellogg Company
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/snef.jpeg
SNEF
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
Kellogg Company
100%
Compliance Rate
0/4 Standards Verified
SNEF
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Manufacturing Industry Average (This Year)

No incidents recorded for Kellogg Company in 2025.

Incidents vs Manufacturing Industry Average (This Year)

No incidents recorded for SNEF in 2025.

Incident History — Kellogg Company (X = Date, Y = Severity)

Kellogg Company cyber incidents detection timeline including parent company and subsidiaries

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

SNEF cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kellogg-company.jpeg
Kellogg Company
Incidents

No Incident

https://images.rankiteo.com/companyimages/snef.jpeg
SNEF
Incidents

No Incident

FAQ

Kellogg Company company demonstrates a stronger AI Cybersecurity Score compared to SNEF company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, SNEF company has disclosed a higher number of cyber incidents compared to Kellogg Company company.

In the current year, SNEF company and Kellogg Company company have not reported any cyber incidents.

Neither SNEF company nor Kellogg Company company has reported experiencing a ransomware attack publicly.

Neither SNEF company nor Kellogg Company company has reported experiencing a data breach publicly.

Neither SNEF company nor Kellogg Company company has reported experiencing targeted cyberattacks publicly.

Neither Kellogg Company company nor SNEF company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kellogg Company nor SNEF holds any compliance certifications.

Neither company holds any compliance certifications.

Kellogg Company company has more subsidiaries worldwide compared to SNEF company.

Kellogg Company company employs more people globally than SNEF company, reflecting its scale as a Manufacturing.

Neither Kellogg Company nor SNEF holds SOC 2 Type 1 certification.

Neither Kellogg Company nor SNEF holds SOC 2 Type 2 certification.

Neither Kellogg Company nor SNEF holds ISO 27001 certification.

Neither Kellogg Company nor SNEF holds PCI DSS certification.

Neither Kellogg Company nor SNEF holds HIPAA certification.

Neither Kellogg Company nor SNEF 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