Comparison Overview

Parfums Christian Dior

VS

The Estée Lauder Companies Inc.

Parfums Christian Dior

190, Avenue Charles de Gaulle, None, Neuilly-sur-Seine, Île-de-France, FR, 92200
Last Update: 2025-11-20
Between 600 and 649

Christian Dior described himself as a fashion and perfume designer. The House of Dior, founded in 1946, changed the face of style forever when its New Look was unveiled in the halls of 30 Avenue Montaigne on February 12th, 1947. The revolutionary look was accompanied by a fragrance, Miss Dior. This timeless perfume was the first fragrance created by a visionary brand which invented the concept of global beauty. The spirit of Dior is reflected in each of the House's products and in the care taken at every stage of their production. From Grasse to Paris to the Dior Gardens, Parfums Christian Dior enhances the most beautiful ingredients so that each of its creations helps shape its global aura. The House of Dior embodies passion, excellence, creativity, diversity, and collaboration. These values, so dear to the House, are at the heart of all Parfums Christian Dior’s activities. The Dior spirit is characterized by a professional environment of excellence where innovation and know-how have a primordial place. Day after day, all the Dior teams around the world are encouraged to be visionary, creative, audacious and agile. Thus, the House of Dior has always invested in employees to reveal their talent and personality, to build together, the Dior of tomorrow.

NAICS: 32562
NAICS Definition: Toilet Preparation Manufacturing
Employees: 8,441
Subsidiaries: 0
12-month incidents
2
Known data breaches
3
Attack type number
2

The Estée Lauder Companies Inc.

767 5th Ave, New York, NY, US, 10153
Last Update: 2025-11-24
Between 700 and 749

The Estée Lauder Companies Inc. is one of the world’s leading manufacturers, marketers, and sellers of quality skin care, makeup, fragrance, and hair care products, and is a steward of outstanding luxury and prestige brands globally. The company’s products are sold in approximately 150 countries and territories under brand names including: Estée Lauder, Aramis, Clinique, Lab Series, Origins, M·A·C, La Mer, Bobbi Brown Cosmetics, Aveda, Jo Malone London, Bumble and bumble, Darphin Paris, TOM FORD, Smashbox, AERIN Beauty, Le Labo, Editions de Parfums Frédéric Malle, GLAMGLOW, KILIAN PARIS, Too Faced, Dr.Jart+, the DECIEM family of brands, including The Ordinary and NIOD, and BALMAIN Beauty. To explore our current job openings, go to www.elcompanies.com

NAICS: 32562
NAICS Definition: Toilet Preparation Manufacturing
Employees: 50,183
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/parfums-christian-dior.jpeg
Parfums Christian Dior
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/the-estee-lauder-companies-inc.jpeg
The Estée Lauder Companies Inc.
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
Parfums Christian Dior
100%
Compliance Rate
0/4 Standards Verified
The Estée Lauder Companies Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Personal Care Product Manufacturing Industry Average (This Year)

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

Incidents vs Personal Care Product Manufacturing Industry Average (This Year)

No incidents recorded for The Estée Lauder Companies Inc. in 2025.

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

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

Incident History — The Estée Lauder Companies Inc. (X = Date, Y = Severity)

The Estée Lauder Companies Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/parfums-christian-dior.jpeg
Parfums Christian Dior
Incidents

Date Detected: 9/2025
Type:Breach
Motivation: National Security, Social Stability, Data Sovereignty, Economic Protection
Blog: Blog

Date Detected: 1/2025
Type:Breach
Attack Vector: Database Compromise
Motivation: Data Theft
Blog: Blog

Date Detected: 6/2024
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/the-estee-lauder-companies-inc.jpeg
The Estée Lauder Companies Inc.
Incidents

Date Detected: 7/2023
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 5/2023
Type:Breach
Attack Vector: External System Breach
Blog: Blog

FAQ

The Estée Lauder Companies Inc. company demonstrates a stronger AI Cybersecurity Score compared to Parfums Christian Dior company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Parfums Christian Dior company has faced a higher number of disclosed cyber incidents historically compared to The Estée Lauder Companies Inc. company.

In the current year, Parfums Christian Dior company has reported more cyber incidents than The Estée Lauder Companies Inc. company.

Neither The Estée Lauder Companies Inc. company nor Parfums Christian Dior company has reported experiencing a ransomware attack publicly.

Both The Estée Lauder Companies Inc. company and Parfums Christian Dior company have disclosed experiencing at least one data breach.

Parfums Christian Dior company has reported targeted cyberattacks, while The Estée Lauder Companies Inc. company has not reported such incidents publicly.

Neither Parfums Christian Dior company nor The Estée Lauder Companies Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Parfums Christian Dior company nor The Estée Lauder Companies Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

The Estée Lauder Companies Inc. company employs more people globally than Parfums Christian Dior company, reflecting its scale as a Personal Care Product Manufacturing.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds SOC 2 Type 1 certification.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds SOC 2 Type 2 certification.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds ISO 27001 certification.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds PCI DSS certification.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. holds HIPAA certification.

Neither Parfums Christian Dior nor The Estée Lauder Companies Inc. 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