Comparison Overview

Moutai China

VS

Pernod Ricard

Moutai China

盐务街 2号 贵阳市, 贵州省 550000, CN
Last Update: 2025-12-09
Between 850 and 899

Moutai is well-known for Chinese National Liquor in Kweichow Province, China. It has long history in liquor brewing, and popular as the Moutai-flavor liquor worldwide. In 2015, Moutai create it's Facebook homepage as "Moutai China", on which fans can find more comprehensive Moutai. Facebook link: https://www.facebook.com/pages/Moutai-China/1553764361514018

NAICS: 3121
NAICS Definition: Beverage Manufacturing
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Pernod Ricard

5 cour Paul Ricard, None, Paris, Ile-de-France, FR, 75008
Last Update: 2025-12-09
Between 800 and 849

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 worldwide with our own salesforce in 73 countries. Our portfolio is one of the most comprehensive in the market with every major category of wine and spirits, providing Pernod Ricard with a unique competitive advantage. To keep growing our business, transforming our industry and making a positive impact on the world, we believe in the power of human connection. Creating ‘convivialité’ is our business and our raison d’être. As ‘créateurs de convivialité’, our purpose is to turn every social interaction into a genuine, friendly and responsible experience of sharing. We believe there can be no convivialité with excess and strive to be sustainable and responsible at every step, from grain to glass. You must be of legal drinking age to follow and only share with others of age. Enjoy our brands responsibly. UGC policy: https://bit.ly/41XEYbx

NAICS: 3121
NAICS Definition: Beverage Manufacturing
Employees: 19,581
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/moutai-china.jpeg
Moutai China
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/pernod-ricard.jpeg
Pernod Ricard
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
Moutai China
100%
Compliance Rate
0/4 Standards Verified
Pernod Ricard
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Beverage Manufacturing Industry Average (This Year)

No incidents recorded for Moutai China in 2025.

Incidents vs Beverage Manufacturing Industry Average (This Year)

No incidents recorded for Pernod Ricard in 2025.

Incident History — Moutai China (X = Date, Y = Severity)

Moutai China 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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/moutai-china.jpeg
Moutai China
Incidents

No Incident

https://images.rankiteo.com/companyimages/pernod-ricard.jpeg
Pernod Ricard
Incidents

No Incident

FAQ

Moutai China company demonstrates a stronger AI Cybersecurity Score compared to Pernod Ricard company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Pernod Ricard company has disclosed a higher number of cyber incidents compared to Moutai China company.

In the current year, Pernod Ricard company and Moutai China company have not reported any cyber incidents.

Neither Pernod Ricard company nor Moutai China company has reported experiencing a ransomware attack publicly.

Neither Pernod Ricard company nor Moutai China company has reported experiencing a data breach publicly.

Neither Pernod Ricard company nor Moutai China company has reported experiencing targeted cyberattacks publicly.

Neither Moutai China company nor Pernod Ricard company has reported experiencing or disclosing vulnerabilities publicly.

Neither Moutai China nor Pernod Ricard holds any compliance certifications.

Neither company holds any compliance certifications.

Pernod Ricard company has more subsidiaries worldwide compared to Moutai China company.

Pernod Ricard company employs more people globally than Moutai China company, reflecting its scale as a Beverage Manufacturing.

Neither Moutai China nor Pernod Ricard holds SOC 2 Type 1 certification.

Neither Moutai China nor Pernod Ricard holds SOC 2 Type 2 certification.

Neither Moutai China nor Pernod Ricard holds ISO 27001 certification.

Neither Moutai China nor Pernod Ricard holds PCI DSS certification.

Neither Moutai China nor Pernod Ricard holds HIPAA certification.

Neither Moutai China nor Pernod Ricard 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