Comparison Overview

BHP

VS

Glencore

BHP

171 Collins Street, Melbourne, 3000, AU
Last Update: 2026-04-01
Between 800 and 849

We are supplying the resources the world needs to help build a better, clearer future. Copper for renewable energy. Potash for sustainable farming. Iron ore and metallurgical coal for the steel needed for global infrastructure and the energy transition. #FutureIsClear Across our global operations, we are committed to working in ways that are true to our BHP Charter values of Sustainability, Integrity, Respect, Performance, Simplicity and Accountability. Learn more about working at BHP and the exciting career opportunities that exist for professionals, undergraduates and graduates on our website: www.bhp.com.

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

Glencore

Baarermattstrasse 3, Baar, 6340, CH
Last Update: 2026-04-01
Between 800 and 849

Glencore is one of the world’s largest global diversified natural resource companies and a major producer and marketer of more than 60 commodities that advance everyday life. Through a network of assets, customers and suppliers that spans the globe, we produce, process, recycle, source, market and distribute the commodities that support decarbonisation while meeting the energy needs of today.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bhp.jpeg
BHP
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/glencore.jpeg
Glencore
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
BHP
100%
Compliance Rate
0/4 Standards Verified
Glencore
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mining Industry Average (This Year)

No incidents recorded for BHP in 2026.

Incidents vs Mining Industry Average (This Year)

No incidents recorded for Glencore in 2026.

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

BHP cyber incidents detection timeline including parent company and subsidiaries

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

Glencore cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bhp.jpeg
BHP
Incidents

No Incident

https://images.rankiteo.com/companyimages/glencore.jpeg
Glencore
Incidents

No Incident

FAQ

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

Historically, Glencore company has disclosed a higher number of cyber incidents compared to BHP company.

In the current year, Glencore company and BHP company have not reported any cyber incidents.

Neither Glencore company nor BHP company has reported experiencing a ransomware attack publicly.

Neither Glencore company nor BHP company has reported experiencing a data breach publicly.

Neither Glencore company nor BHP company has reported experiencing targeted cyberattacks publicly.

Neither BHP company nor Glencore company has reported experiencing or disclosing vulnerabilities publicly.

Neither BHP nor Glencore holds any compliance certifications.

Neither company holds any compliance certifications.

Glencore company has more subsidiaries worldwide compared to BHP company.

BHP company employs more people globally than Glencore company, reflecting its scale as a Mining.

Neither BHP nor Glencore holds SOC 2 Type 1 certification.

Neither BHP nor Glencore holds SOC 2 Type 2 certification.

Neither BHP nor Glencore holds ISO 27001 certification.

Neither BHP nor Glencore holds PCI DSS certification.

Neither BHP nor Glencore holds HIPAA certification.

Neither BHP nor Glencore holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H