Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download

Comparison Overview

CHANELCHANEL
VS
HermèsHermès
CHANEL

CHANEL

London, W1J 6TL, GB

Last Update: 30/06/2026

View Profile
Between 700 and 749
http://www.chanel.com
700/1000Moderate

Chanel is a private company and world leader in creating, manufacturing and distributing luxury products, including Ready-to-Wear, Accessories, Fragrances, Makeup, Skincare, Jewellery and Watches. Founded by Gabrielle Chanel in 1910, the House remains dedicated to excep...

NAICS:4483
NAICS Definition:Jewelry, Luggage, and Leather Goods Stores
Employees:29,361
Subsidiaries:0
12-month incidents
0
Known data breaches
4
Attack type number
1
Hermès

Hermès

24, rue du Faubourg-Saint-Honoré, Paris, 75008, FR

Last Update: 07/08/2026

View Profile
842/1000Good

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 fr...

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

Compliance Ranges Comparison

Based On Specific Ai Models Category
CHANEL

CHANEL

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA
Hermès

Hermès

-
ISO 27001Not verified
ISO 27001
-
SOC2 Type 1Not verified
SOC2 Type 1
-
SOC2 Type 2Not verified
SOC2 Type 2
-
GDPRNot verified
GDPR
-
PCI DSSNot verified
PCI DSS
-
HIPAANot verified
HIPAA

Benchmark & Cyber Underwriting Signals

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

No incidents recorded for CHANEL in 2026.

Incidents

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

No incidents recorded for Hermès in 2026.

Incidents

Incident History - CHANEL (X = Date, Y = Severity)

CHANEL cyber incidents detection timeline including parent company and subsidiaries.

R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

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

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

No timeline data available
R - Ransomware
C - Cyber Attack
D - Data Breach
V - Vulnerability

Notable Incidents

Last Cyber / HR Incidents / Global...
CHANEL

CHANEL

Incidents
🔒 Incident : Breach
GAI1122911112425
🔒 Incident : Breach
CHA340080725
🔒 Incident : Breach
GAI0292402112125
Hermès

Hermès

Incidents
No explicit notable incidents reported.

FAQ

Between CHANEL company and Hermès company, which one has the best AI Cybersecurity Score ?
Between CHANEL company and Hermès company, which one has experienced more cyber incidents in the past ?
Between CHANEL company and Hermès company, which one has experienced more cyber incidents this year ?
Between CHANEL company and Hermès company, which one has experienced at least one ransomware attack ?
Between CHANEL company and Hermès company, which one has experienced at least one data breach ?
Between CHANEL company and Hermès company, which one has experienced at least one targeted cyberattack ?
Between CHANEL company and Hermès company, which one has experienced at least one vulnerability ?
Between CHANEL company and Hermès company, which one holds the most compliance certifications ?
Between CHANEL company and Hermès company, which one holds the fewest compliance certifications ?
Between CHANEL company and Hermès company, which one has the most subsidiaries ?
Between CHANEL company and Hermès company, which one has the largest number of employees ?
Between CHANEL and Hermès, which company holds both SOC 2 Type 1 certifications ?
Between CHANEL and Hermès, which company holds both SOC 2 Type 2 certifications ?
Which company is ISO 27001 certified - CHANEL or Hermès ?
Which company is PCI DSS compliant - CHANEL or Hermès ?
Between CHANEL and Hermès, which company complies with HIPAA regulations for healthcare data ?
Between CHANEL and Hermès, which company complies with GDPR requirements ?

Latest Global CVEs

CVE-2026-74250
SUMMARY

In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 6.3)
CVSS3
Base Score: 6.3
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
IMPACT SCORE
4
EXPLOITABILITY
1.8
CVE-2026-74247
SUMMARY

A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 4.2)
CVSS3
Base Score: 4.2
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
IMPACT SCORE
2.5
EXPLOITABILITY
1.6
CVE-2026-74245
SUMMARY

A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 5.9)
CVSS3
Base Score: 5.9
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
2.2
CVE-2026-74244
SUMMARY

A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 5.9)
CVSS3
Base Score: 5.9
Complexity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
IMPACT SCORE
3.6
EXPLOITABILITY
2.2
CVE-2026-74243
SUMMARY

A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.

PUBLISHED
Date2026-08-14
UPDATED
Date2026-08-14
RISK INFORMATION (Score: 6.5)
CVSS3
Base Score: 6.5
Complexity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
IMPACT SCORE
2.5
EXPLOITABILITY
3.9