Comparison Overview

Kroger

VS

Specsavers

Kroger

1014 Vine Street, None, Cincinnati, Ohio, US, 45202
Last Update: 2025-11-27
Between 750 and 799

At Kroger, we believe no matter who you are or how you like to shop, everyone deserves affordable, easy-to-enjoy, fresh food. This idea is embodied in our simple tagline—Fresh for Everyone™. Kroger ranks as one of the world’s largest retailers. We are nearly half a million associates across 2,800 stores in 35 states operating two dozen grocery retail brands and 34 manufacturing and 44 distribution locations, all dedicated to living our Purpose: to Feed the Human Spirit™. Together, we serve more than 11 million customers daily in our stores and online through convenient e-commerce options like pickup, ship and delivery, serving America through food inspiration and uplift. Customers love Our Brands, including the popular Kroger®, Private Selection® and Simple Truth® brands. Our own manufacturing plants produce many of Our Brands products, including breads, dairy products, meat and thousands of grocery items. We also believe in and are committed to doing our part to create #ZeroHungerZeroWaste communities by 2025. To learn more about us or apply for a job, visit TheKrogerCo.com.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 138,271
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
2

Specsavers

La Villiaize, Global, undefined, GY6 8YP, GB
Last Update: 2025-11-27
Between 750 and 799

Specsavers began 40 years ago with the vision of two optometrists, Doug and Mary Perkins, who set out to provide best-value eyecare to everybody. Their passion for optometry has led Specsavers to become the largest privately-owned optical group in the world, delivering high-quality, affordable optical and hearing care in 12 countries. And it continues to shape the lives and experience of around 41,000 colleagues who are developing their careers with us across the globe.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 25,337
Subsidiaries: 6
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/kroger.jpeg
Kroger
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/specsavers.jpeg
Specsavers
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
Kroger
100%
Compliance Rate
0/4 Standards Verified
Specsavers
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Kroger in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Specsavers in 2025.

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

Kroger cyber incidents detection timeline including parent company and subsidiaries

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

Specsavers cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kroger.jpeg
Kroger
Incidents

Date Detected: 02/2021
Type:Breach
Attack Vector: Hacked File Transfer Service
Blog: Blog

Date Detected: 12/2020
Type:Cyber Attack
Attack Vector: Malware
Blog: Blog
https://images.rankiteo.com/companyimages/specsavers.jpeg
Specsavers
Incidents

Date Detected: 06/2019
Type:Data Leak
Attack Vector: Physical Theft
Blog: Blog

FAQ

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

Kroger company has faced a higher number of disclosed cyber incidents historically compared to Specsavers company.

In the current year, Specsavers company and Kroger company have not reported any cyber incidents.

Neither Specsavers company nor Kroger company has reported experiencing a ransomware attack publicly.

Kroger company has disclosed at least one data breach, while the other Specsavers company has not reported such incidents publicly.

Kroger company has reported targeted cyberattacks, while Specsavers company has not reported such incidents publicly.

Neither Kroger company nor Specsavers company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kroger nor Specsavers holds any compliance certifications.

Neither company holds any compliance certifications.

Specsavers company has more subsidiaries worldwide compared to Kroger company.

Kroger company employs more people globally than Specsavers company, reflecting its scale as a Retail.

Neither Kroger nor Specsavers holds SOC 2 Type 1 certification.

Neither Kroger nor Specsavers holds SOC 2 Type 2 certification.

Neither Kroger nor Specsavers holds ISO 27001 certification.

Neither Kroger nor Specsavers holds PCI DSS certification.

Neither Kroger nor Specsavers holds HIPAA certification.

Neither Kroger nor Specsavers 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