Comparison Overview

China Shenhua Energy Co., Ltd.

VS

Eramet

China Shenhua Energy Co., Ltd.

22 Xibinhe Road Andingmen, Dongcheng District, None, BEIJING, BEJ, CN, 100011
Last Update: 2025-11-26
Between 800 and 849

China Shenhua Energy is a mining & metals company based out of BEIJING, BEJ, China.

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

Eramet

10, Boulevard de Grenelle Paris, Ile-de-France 75015, FR
Last Update: 2025-11-26
Between 750 and 799

Committed to sustainable metals. Eramet transforme les ressources minérales de la Terre pour apporter des solutions durables et responsables à la croissance de l’industrie et aux défis de la transition énergétique Ses collaborateurs s’y engagent par leur démarche citoyenne et contributive dans l’ensemble des pays où le groupe minier et métallurgique est présent : France, Argentine, Gabon, Sénégal, Nouvelle-Calédonie, Indonésie, Norvège, USA. Manganèse, nickel, sables minéralisés, lithium et cobalt : Eramet valorise et développe les métaux indispensables à la construction d’un monde plus durable. Partenaire privilégié de ses clients industriels, le Groupe contribue à rendre les infrastructures et les constructions robustes et résistantes, les moyens de mobilité plus performants, les outils de santé plus sûrs, les appareils de télécommunications plus efficaces. Pleinement engagé dans l’ère des métaux, Eramet ambitionne de devenir une référence de la transformation responsable des ressources minérales de la Terre, pour le bien vivre ensemble.

NAICS: 212
NAICS Definition:
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/china-shenhua-energy-co-ltd-.jpeg
China Shenhua Energy Co., Ltd.
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/eramet.jpeg
Eramet
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
China Shenhua Energy Co., Ltd.
100%
Compliance Rate
0/4 Standards Verified
Eramet
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mining Industry Average (This Year)

No incidents recorded for China Shenhua Energy Co., Ltd. in 2025.

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Eramet in 2025.

Incident History — China Shenhua Energy Co., Ltd. (X = Date, Y = Severity)

China Shenhua Energy Co., Ltd. cyber incidents detection timeline including parent company and subsidiaries

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

Eramet cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/china-shenhua-energy-co-ltd-.jpeg
China Shenhua Energy Co., Ltd.
Incidents

No Incident

https://images.rankiteo.com/companyimages/eramet.jpeg
Eramet
Incidents

No Incident

FAQ

China Shenhua Energy Co., Ltd. company demonstrates a stronger AI Cybersecurity Score compared to Eramet company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Eramet company has disclosed a higher number of cyber incidents compared to China Shenhua Energy Co., Ltd. company.

In the current year, Eramet company and China Shenhua Energy Co., Ltd. company have not reported any cyber incidents.

Neither Eramet company nor China Shenhua Energy Co., Ltd. company has reported experiencing a ransomware attack publicly.

Neither Eramet company nor China Shenhua Energy Co., Ltd. company has reported experiencing a data breach publicly.

Neither Eramet company nor China Shenhua Energy Co., Ltd. company has reported experiencing targeted cyberattacks publicly.

Neither China Shenhua Energy Co., Ltd. company nor Eramet company has reported experiencing or disclosing vulnerabilities publicly.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds any compliance certifications.

Neither company holds any compliance certifications.

Neither China Shenhua Energy Co., Ltd. company nor Eramet company has publicly disclosed detailed information about the number of their subsidiaries.

Eramet company employs more people globally than China Shenhua Energy Co., Ltd. company, reflecting its scale as a Mining.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds SOC 2 Type 1 certification.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds SOC 2 Type 2 certification.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds ISO 27001 certification.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds PCI DSS certification.

Neither China Shenhua Energy Co., Ltd. nor Eramet holds HIPAA certification.

Neither China Shenhua Energy Co., Ltd. nor Eramet 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