Comparison Overview

LVMH

VS

Christian Dior Couture

LVMH

22, avenue Montaigne, None, Paris, None, FR, 75008
Last Update: 2025-11-27
Between 800 and 849

LVMH is the world leader in luxury. A family group founded in 1987 and headed by Chairman and CEO Bernard Arnault, LVMH is now home to 75 iconic Maisons, which embody a distinctive art de vivre blending heritage and modernity. With reported sales of 86.2 billion euros in 2023 and 6000 stores around the world, we are the only group present in all major sectors of the luxury industry: Wines & Spirits, Fashion & Leather Goods, Perfumes & Cosmetics, Watches & Jewelry, Selective Distribution. Our long-term vision, entrepreneurial spirit and constant search for new solutions set us apart. The success of our Group is only possible thanks to our employees: 213,000 passionate and committed women and men, representing 190 nationalities, work in our studios, workshops, wineries, factories, offices and boutiques all around the world. Their talent and their diversity are our strength. Being part of LVMH means being continuously inspired by our heritage, creativity and sense of the collective. We have exceptional stories to share and an unrivalled legacy to pass on to future generations. Being part of LVMH means being challenged. We set ambitious paths to excellence by continuously pushing the boundaries, raising our standards and renewing ourselves to ensure the long-term development of our Maisons. Being part of LVMH means belonging to one of the world’s most creative and innovative communities. We foster collaborations that enable our people to enrich their knowledge, grow their network and share their passions. Being part of LVMH means being supported in an inclusive and diverse workplace, where all voices are heard and each talent is given the means to thrive. In 6 different industries, across 81 countries, LVMH and its Maisons are committed to exemplary ethics, social and environmental responsibility. We strive to ensure that our products and the way they are made have positive impact on our entire ecosystem and on our host communities. At LVMH, we craft the future.

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

Christian Dior Couture

30 avenue Montaigne, Paris, Île de France, FR, 75008
Last Update: 2025-11-26

Welcome to Christian Dior Couture, House of Dreams, House of Talents. Christian Dior was the designer of dreams. In founding his House in 1947, marked by the revolution of the New Look, he metamorphosed his reveries into wonderful creations. His visionary spirit never ceased to make Clients all over the world feel more beautiful, an inspiration for his successors to this day. Christian Dior Couture, the House of Dreams, is recognized for its French heritage & vibrant culture sublimating its unique Savoir-faire and Creativity through empowering "metiers d’art”. Our Maison is a destination for sustainable growth & success where we shape the future of our Talents in a positive, authentic & generous environment. We bloom & deliver excellence with passion, determination, courage & optimism to offer meaningful & daring codes. Rich in exceptional heritage, with a community of more than 12000 talents, our House embodies Christian Dior’s “House of Talents” today more than ever.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/lvmh.jpeg
LVMH
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/christian-dior-couture.jpeg
Christian Dior Couture
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
LVMH
100%
Compliance Rate
0/4 Standards Verified
Christian Dior Couture
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

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

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

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

Christian Dior Couture has 545.16% more incidents than the average of same-industry companies with at least one recorded incident.

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

LVMH cyber incidents detection timeline including parent company and subsidiaries

Incident History — Christian Dior Couture (X = Date, Y = Severity)

Christian Dior Couture cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/lvmh.jpeg
LVMH
Incidents

Date Detected: 7/2025
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/christian-dior-couture.jpeg
Christian Dior Couture
Incidents

Date Detected: 9/2025
Type:Breach
Blog: Blog

Date Detected: 5/2025
Type:Cyber Attack
Blog: Blog

Date Detected: 1/2025
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

FAQ

LVMH company demonstrates a stronger AI Cybersecurity Score compared to Christian Dior Couture company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Christian Dior Couture company has faced a higher number of disclosed cyber incidents historically compared to LVMH company.

In the current year, Christian Dior Couture company has reported more cyber incidents than LVMH company.

Neither Christian Dior Couture company nor LVMH company has reported experiencing a ransomware attack publicly.

Both Christian Dior Couture company and LVMH company have disclosed experiencing at least one data breach.

Christian Dior Couture company has reported targeted cyberattacks, while LVMH company has not reported such incidents publicly.

Neither LVMH company nor Christian Dior Couture company has reported experiencing or disclosing vulnerabilities publicly.

Neither LVMH nor Christian Dior Couture holds any compliance certifications.

Neither company holds any compliance certifications.

Neither LVMH company nor Christian Dior Couture company has publicly disclosed detailed information about the number of their subsidiaries.

LVMH company employs more people globally than Christian Dior Couture company, reflecting its scale as a Retail Luxury Goods and Jewelry.

Neither LVMH nor Christian Dior Couture holds SOC 2 Type 1 certification.

Neither LVMH nor Christian Dior Couture holds SOC 2 Type 2 certification.

Neither LVMH nor Christian Dior Couture holds ISO 27001 certification.

Neither LVMH nor Christian Dior Couture holds PCI DSS certification.

Neither LVMH nor Christian Dior Couture holds HIPAA certification.

Neither LVMH nor Christian Dior Couture 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