Comparison Overview

Moutai China

VS

Diageo

Moutai China

盐务街 2号 贵阳市, 贵州省 550000, CN
Last Update: 2025-11-27
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

Diageo

Lakeside Drive, London, undefined, NW10 7HQ, GB
Last Update: 2025-11-27
Between 800 and 849

Diageo's official LinkedIn account. We're a global leader in premium drinks, across spirits and beer, a business built on the principles and foundations laid by the giants of the industry. With over 200 brands sold in 180 countries, our portfolio has remarkable breadth. From centuries-old names to exciting new entrants, and global giants to local legends, we're building the very best brands out there, and with over 30,000 talented people based in over 135 countries, we're a truly global company. With such diversity, we're able to truly represent our broad consumer base and think differently about the future. To maintain our position as leaders in the alcoholic beverage market, we always invest in the future and are mindful of the impact we have. Because just like the legends of our past, we're here to raise the bar – for people as well as the planet.

NAICS: 3121
NAICS Definition: Beverage Manufacturing
Employees: 33,077
Subsidiaries: 8
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/diageo.jpeg
Diageo
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
Diageo
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 Diageo in 2025.

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

Moutai China cyber incidents detection timeline including parent company and subsidiaries

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

Diageo 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/diageo.jpeg
Diageo
Incidents

No Incident

FAQ

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

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

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

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

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

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

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

Neither Moutai China nor Diageo holds any compliance certifications.

Neither company holds any compliance certifications.

Diageo company has more subsidiaries worldwide compared to Moutai China company.

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

Neither Moutai China nor Diageo holds SOC 2 Type 1 certification.

Neither Moutai China nor Diageo holds SOC 2 Type 2 certification.

Neither Moutai China nor Diageo holds ISO 27001 certification.

Neither Moutai China nor Diageo holds PCI DSS certification.

Neither Moutai China nor Diageo holds HIPAA certification.

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