Comparison Overview

Fozzy Group

VS

Whole Foods Market

Fozzy Group

13 Kalachevskaya Str. Kiev, 02090, UA
Last Update: 2026-01-18
Between 750 and 799

Fozzy Group is one of the largest trade industrial groups in Ukraine and one of the leading Ukrainian retailers, with over 700 outlets all around the country. Besides retail, the group's businesses include food production, and restaurants. Fozzy Group is introducing modern solutions in all areas of its activity. By investing in improving its business processes, the group has achieved leading positions in the retail market. By performing retail chains logistics through its own distribution centers, Fozzy Group has been able to ensure the timely delivery of food to its stores all over Ukraine. In addition, the group operates its own quality control system, ensuring full compliance with its standards in goods storage, transportation and sale. Since its inception in 1997, Fozzy Group has focused on making innovative business improvements, creating new opportunities for the market and further developing the industry as a whole.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Whole Foods Market

550 Bowie st, Austin, TX, US, 78701
Last Update: 2026-01-24

Whole Foods was founded in 1980 on the belief that where food comes from, and how it’s grown, matters. It meant creating quality standards, working with suppliers who achieve them, and sharing that information with our customers. And it radically changed the way people understood and shopped for food. The result has been the highest quality natural and organic products, an unmatched experience in more than 500+ stores, with a passionate team of over 90,000 team members, 5 percent of our total net profits given back to our communities each year, and millions of customers who put their trust in us every day.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/fozzy-group.jpeg
Fozzy Group
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/whole-foods-market.jpeg
Whole Foods Market
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
Fozzy Group
100%
Compliance Rate
0/4 Standards Verified
Whole Foods Market
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Fozzy Group in 2026.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Whole Foods Market in 2026.

Incident History — Fozzy Group (X = Date, Y = Severity)

Fozzy Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — Whole Foods Market (X = Date, Y = Severity)

Whole Foods Market cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/fozzy-group.jpeg
Fozzy Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/whole-foods-market.jpeg
Whole Foods Market
Incidents

Date Detected: 09/2023
Type:Breach
Attack Vector: Payment Card Systems
Motivation: Financial Gain
Blog: Blog

Date Detected: 3/2017
Type:Breach
Blog: Blog

FAQ

Fozzy Group company demonstrates a stronger AI Cybersecurity Score compared to Whole Foods Market company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Whole Foods Market company has historically faced a number of disclosed cyber incidents, whereas Fozzy Group company has not reported any.

In the current year, Whole Foods Market company and Fozzy Group company have not reported any cyber incidents.

Neither Whole Foods Market company nor Fozzy Group company has reported experiencing a ransomware attack publicly.

Whole Foods Market company has disclosed at least one data breach, while Fozzy Group company has not reported such incidents publicly.

Neither Whole Foods Market company nor Fozzy Group company has reported experiencing targeted cyberattacks publicly.

Neither Fozzy Group company nor Whole Foods Market company has reported experiencing or disclosing vulnerabilities publicly.

Neither Fozzy Group nor Whole Foods Market holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Fozzy Group company nor Whole Foods Market company has publicly disclosed detailed information about the number of their subsidiaries.

Whole Foods Market company employs more people globally than Fozzy Group company, reflecting its scale as a Retail.

Neither Fozzy Group nor Whole Foods Market holds SOC 2 Type 1 certification.

Neither Fozzy Group nor Whole Foods Market holds SOC 2 Type 2 certification.

Neither Fozzy Group nor Whole Foods Market holds ISO 27001 certification.

Neither Fozzy Group nor Whole Foods Market holds PCI DSS certification.

Neither Fozzy Group nor Whole Foods Market holds HIPAA certification.

Neither Fozzy Group nor Whole Foods Market holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

Risk Information
cvss3
Base: 5.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.