Comparison Overview

Grupo México

VS

UC RUSAL

Grupo México

Campos Elíseos 400, Ciudad de México, México, 11000, MX
Last Update: 2025-11-26
Between 800 and 849

Somos una empresa líder en producción de cobre, transporte ferroviario e infraestructura. A lo largo de 80 años, hemos evolucionado y nos hemos diversificado para convertirnos en una empresa estable, sustentable, siempre a la vanguardia tecnológica. Desde 1966 cotizamos en la Bolsa Mexicana de Valores, con un 40% de capital flotante.

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

UC RUSAL

1, Vasilisy Kozhinoy str. Moscow, 109240, RU
Last Update: 2025-11-24
Between 750 and 799

RUSAL is a leading global producer of low-carbon aluminium. More than 90% of the Company's aluminium is produced from renewable electricity, and by implementing innovative and energy-saving technologies RUSAL is able to reduce greenhouse gas emissions at all production stages. This has enabled RUSAL to become one of the first in the world to master the production of 'green' metal under the ALLOW brand. Less than 4 t of CO2 equivalent per 1 tonne of aluminium is the carbon footprint of ALLOW aluminium brand (scope 1 and scope 2) RUSAL operates in 20 countries on 5 continents. The company employs 50,000 people across the globe. In 2020, RUSAL accounted for approximately 5.8% of global production of aluminium and 6.5% of alumina. The Company’s key sales markets are Europe, Russia and the CIS countries, North America, South-East Asia, Japan and South Korea. The major end users are transport, construction, power and packaging industries. RUSAL owns proprietary smelting technologies and is developing new ones, including a revolutionary inert anode technology.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/grupo-mexico.jpeg
Grupo México
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/uc-rusal.jpeg
UC RUSAL
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
Grupo México
100%
Compliance Rate
0/4 Standards Verified
UC RUSAL
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Grupo México in 2025.

Incidents vs Mining Industry Average (This Year)

No incidents recorded for UC RUSAL in 2025.

Incident History — Grupo México (X = Date, Y = Severity)

Grupo México cyber incidents detection timeline including parent company and subsidiaries

Incident History — UC RUSAL (X = Date, Y = Severity)

UC RUSAL cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/grupo-mexico.jpeg
Grupo México
Incidents

No Incident

https://images.rankiteo.com/companyimages/uc-rusal.jpeg
UC RUSAL
Incidents

No Incident

FAQ

Grupo México company demonstrates a stronger AI Cybersecurity Score compared to UC RUSAL company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, UC RUSAL company has disclosed a higher number of cyber incidents compared to Grupo México company.

In the current year, UC RUSAL company and Grupo México company have not reported any cyber incidents.

Neither UC RUSAL company nor Grupo México company has reported experiencing a ransomware attack publicly.

Neither UC RUSAL company nor Grupo México company has reported experiencing a data breach publicly.

Neither UC RUSAL company nor Grupo México company has reported experiencing targeted cyberattacks publicly.

Neither Grupo México company nor UC RUSAL company has reported experiencing or disclosing vulnerabilities publicly.

Neither Grupo México nor UC RUSAL holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Grupo México company nor UC RUSAL company has publicly disclosed detailed information about the number of their subsidiaries.

UC RUSAL company employs more people globally than Grupo México company, reflecting its scale as a Mining.

Neither Grupo México nor UC RUSAL holds SOC 2 Type 1 certification.

Neither Grupo México nor UC RUSAL holds SOC 2 Type 2 certification.

Neither Grupo México nor UC RUSAL holds ISO 27001 certification.

Neither Grupo México nor UC RUSAL holds PCI DSS certification.

Neither Grupo México nor UC RUSAL holds HIPAA certification.

Neither Grupo México nor UC RUSAL 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