Comparison Overview
Champagne Laurent-Perrier

Champagne Laurent-Perrier
32, Avenue de Champagne, Tours-sur-Marne, Grand Est, 51150, FR
Last Update: 19/03/2026
Laurent-Perrier is an independent family House that was built with 4 strong convictions. These 4 convictions make Laurent-Perrier, through its Cuvées, very different from other Champagne Houses. The blend, not the vintage Blending is the real secret of Champagne region...

Pernod Ricard
5 cour Paul Ricard, Paris, 75008, FR
Last Update: 13/07/2026
Pernod Ricard is a convivial, responsible and successful global wine and spirits group and the #1 premium spirits organisation in the world. The Group represents 240 premium brands available in more than 160 countries. We are 18,500 exceptionally talented people worldwi...
Compliance Ranges Comparison

Champagne Laurent-Perrier







Pernod Ricard






Benchmark & Cyber Underwriting Signals
Incidents vs Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Champagne Laurent-Perrier in 2026.
Incidents vs Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Pernod Ricard in 2026.
Incident History - Champagne Laurent-Perrier (X = Date, Y = Severity)
Champagne Laurent-Perrier cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pernod Ricard (X = Date, Y = Severity)
Pernod Ricard cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Champagne Laurent-Perrier

Pernod Ricard
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.