Comparison Overview

Rio Tinto

VS

CMOC

Rio Tinto

6 St James's Square, London, Greater London, SW1Y 4AD, GB
Last Update: 2025-11-26
Between 800 and 849

We're finding better ways to provide the materials the world needs. Iron ore for steel. Low carbon aluminium for electric cars and smartphones. Copper for wind turbines, electric cars and the pipes that bring water to our home. Borates that help crops grow and titanium for paint.

NAICS: 212
NAICS Definition: Mining (except Oil and Gas)
Employees: 38,657
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

CMOC

Au Nord De Yihe, Route Huamei Shan Luanchuan, Henan 471500, CN
Last Update: 2025-11-26
Between 800 and 849

CMOC or CMOC Group Limited is a public holding company created in 1969, engaged in the mining, processing, and trading of base and rare metals. Its main mining assets are located in the Democratic Republic of the Congo (DRC), China and Brazil, and its metal trading business spanned 80 countries, making CMOC one of the world’s largest producers of tungsten, cobalt, niobium and molybdenum, as well as a leading copper producer. CMOC’s vision is to ensure a responsible supply of metals for the sustainable energy sector in order to meet the needs of the global energy transition, as it advocates a more sustainable development for the mining industry and the well-being of humanity. As a key player in the mining industry, CMOC is committed towards the environment - through its innovation to support the ecological transition or its carbon-neutral strategy -, the community - by conducting activities that promotes positive and open relationships with local communities and its support of the United Nations Sustainable Development Goals - and to a responsible governance based on equality respect for international standards and transparency.

NAICS: 212
NAICS Definition: Mining (except Oil and Gas)
Employees: 10,001
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rio-tinto.jpeg
Rio Tinto
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/cmocinternational.jpeg
CMOC
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
Rio Tinto
100%
Compliance Rate
0/4 Standards Verified
CMOC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Rio Tinto in 2025.

Incidents vs Mining Industry Average (This Year)

No incidents recorded for CMOC in 2025.

Incident History — Rio Tinto (X = Date, Y = Severity)

Rio Tinto cyber incidents detection timeline including parent company and subsidiaries

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

CMOC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rio-tinto.jpeg
Rio Tinto
Incidents

No Incident

https://images.rankiteo.com/companyimages/cmocinternational.jpeg
CMOC
Incidents

No Incident

FAQ

Rio Tinto company demonstrates a stronger AI Cybersecurity Score compared to CMOC company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, CMOC company has disclosed a higher number of cyber incidents compared to Rio Tinto company.

In the current year, CMOC company and Rio Tinto company have not reported any cyber incidents.

Neither CMOC company nor Rio Tinto company has reported experiencing a ransomware attack publicly.

Neither CMOC company nor Rio Tinto company has reported experiencing a data breach publicly.

Neither CMOC company nor Rio Tinto company has reported experiencing targeted cyberattacks publicly.

Neither Rio Tinto company nor CMOC company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rio Tinto nor CMOC holds any compliance certifications.

Neither company holds any compliance certifications.

Rio Tinto company has more subsidiaries worldwide compared to CMOC company.

Rio Tinto company employs more people globally than CMOC company, reflecting its scale as a Mining.

Neither Rio Tinto nor CMOC holds SOC 2 Type 1 certification.

Neither Rio Tinto nor CMOC holds SOC 2 Type 2 certification.

Neither Rio Tinto nor CMOC holds ISO 27001 certification.

Neither Rio Tinto nor CMOC holds PCI DSS certification.

Neither Rio Tinto nor CMOC holds HIPAA certification.

Neither Rio Tinto nor CMOC 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