Comparison Overview

Intermarché

VS

Whole Foods Market

Intermarché

21 allée des Mousquetaires, Parc de Tréville, Bondoufle, FR, 91078
Last Update: 2025-11-27

Reconnue pour son combat contre la vie chère, Intermarché s'appuie sur un réseau de 2 328 points de vente en Europe (France, Belgique, Pologne, Portugal). Spécialiste des produits frais, l’enseigne propose différents formats de points de vente pour répondre aux attentes de ses clients : - Intermarché Hyper : un format offrant une gamme complète en alimentaire et en non-alimentaire. - Intermarché Super : deux déclinaisons existent selon la localisation. . Le supermarché généraliste qui propose une offre équilibrée entre alimentaire et non-alimentaire. . Le supermarché alimentaire dont 90 % des produits sont consacrés à l’alimentaire. - Intermarché Contact : un format qui associe l'esprit convivial et le confort d'un commerce de proximité essentiellement en zone rurale. - Intermarché Express : un concept spécialement étudié pour les centres-ville des grandes agglomérations.

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

Whole Foods Market

550 Bowie st, None, Austin, TX, None, US, 78701
Last Update: 2025-11-20

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: 47,551
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/intermarche.jpeg
Intermarché
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
Intermarché
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 Intermarché in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Whole Foods Market in 2025.

Incident History — Intermarché (X = Date, Y = Severity)

Intermarché 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/intermarche.jpeg
Intermarché
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

Intermarché 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 Intermarché company has not reported any.

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

Neither Whole Foods Market company nor Intermarché company has reported experiencing a ransomware attack publicly.

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

Neither Whole Foods Market company nor Intermarché company has reported experiencing targeted cyberattacks publicly.

Neither Intermarché company nor Whole Foods Market company has reported experiencing or disclosing vulnerabilities publicly.

Neither Intermarché nor Whole Foods Market holds any compliance certifications.

Neither company holds any compliance certifications.

Intermarché company has more subsidiaries worldwide compared to Whole Foods Market company.

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

Neither Intermarché nor Whole Foods Market holds SOC 2 Type 1 certification.

Neither Intermarché nor Whole Foods Market holds SOC 2 Type 2 certification.

Neither Intermarché nor Whole Foods Market holds ISO 27001 certification.

Neither Intermarché nor Whole Foods Market holds PCI DSS certification.

Neither Intermarché nor Whole Foods Market holds HIPAA certification.

Neither Intermarché nor Whole Foods Market 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