Comparison Overview

Hermès

VS

Kering

Hermès

24, rue du Faubourg-Saint-Honoré, Paris, undefined, 75008, FR
Last Update: 2025-12-09

A creator, artisan and seller of high-quality objects since 1837, Hermès is an independent, family-owned French house that employs more than 16,600 people worldwide. Driven by its permanent entrepreneurial spirit and consistently high standards, Hermès cultivates the freedom and autonomy of each individual through responsible management. The company perpetuates the transmission of exceptional know-how through strong territorial presence that respects people and nature, a source of exceptional materials. Sixteen artisanal métiers nurture the creativity of the house, whose collections are presented in over 300 stores around the world.

NAICS: 4483
NAICS Definition: Jewelry, Luggage, and Leather Goods Stores
Employees: 16,767
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Kering

40, rue de Sèvres, None, PARIS, None, FR, 75007
Last Update: 2025-12-09
Between 700 and 749

Kering is a global, family-led luxury group, home to people whose passion and expertise nurture creative Houses across ready-to-wear and couture, leather goods, jewelry, eyewear and beauty: Gucci, Saint Laurent, Bottega Veneta, Balenciaga, McQueen, Brioni, Boucheron, Pomellato, Dodo, Qeelin, Ginori 1735, as well as Kering Eyewear and Kering Beauté. Inspired by their creative heritage, Kering’s Houses design and craft exceptional products and experiences that reflect the Group’s commitment to excellence, sustainability and culture. This vision is expressed in our signature: Creativity is our Legacy.

NAICS: 4483
NAICS Definition: Jewelry, Luggage, and Leather Goods Stores
Employees: 37,699
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/hermes-group.jpeg
Hermès
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/kering.jpeg
Kering
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
Hermès
100%
Compliance Rate
0/4 Standards Verified
Kering
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Luxury Goods and Jewelry Industry Average (This Year)

No incidents recorded for Hermès in 2025.

Incidents vs Retail Luxury Goods and Jewelry Industry Average (This Year)

Kering has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Hermès (X = Date, Y = Severity)

Hermès cyber incidents detection timeline including parent company and subsidiaries

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

Kering cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hermes-group.jpeg
Hermès
Incidents

No Incident

https://images.rankiteo.com/companyimages/kering.jpeg
Kering
Incidents

Date Detected: 4/2025
Type:Cyber Attack
Attack Vector: Credential Theft (Salesforce Logins), Social Engineering
Motivation: Financial Gain, Data Exfiltration for Secondary Exploitation
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: Compromised Cloud Account (Salesforce), Credential Theft/Phishing (likely)
Motivation: Financial Gain (Ransom Demand), Data Theft for Resale
Blog: Blog

FAQ

Hermès company demonstrates a stronger AI Cybersecurity Score compared to Kering company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Kering company has historically faced a number of disclosed cyber incidents, whereas Hermès company has not reported any.

In the current year, Kering company has reported more cyber incidents than Hermès company.

Neither Kering company nor Hermès company has reported experiencing a ransomware attack publicly.

Kering company has disclosed at least one data breach, while Hermès company has not reported such incidents publicly.

Kering company has reported targeted cyberattacks, while Hermès company has not reported such incidents publicly.

Neither Hermès company nor Kering company has reported experiencing or disclosing vulnerabilities publicly.

Neither Hermès nor Kering holds any compliance certifications.

Neither company holds any compliance certifications.

Hermès company has more subsidiaries worldwide compared to Kering company.

Kering company employs more people globally than Hermès company, reflecting its scale as a Retail Luxury Goods and Jewelry.

Neither Hermès nor Kering holds SOC 2 Type 1 certification.

Neither Hermès nor Kering holds SOC 2 Type 2 certification.

Neither Hermès nor Kering holds ISO 27001 certification.

Neither Hermès nor Kering holds PCI DSS certification.

Neither Hermès nor Kering holds HIPAA certification.

Neither Hermès nor Kering holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

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

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

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

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

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