Comparison Overview
Sedgman

Sedgman
L5 179 Grey St, South Bank, Queensland, AU, 4101
Last Update: 29/04/2026
Sedgman is the leading provider of integrated minerals processing solutions. Our 250-strong portfolio of high-performing processing plants and supporting mine-site infrastructure showcases the value of our specialist focus. Since 1980, we’ve advanced the standard of exc...

Anglo American
17 Charterhouse Street, London, EC1N 6RA, GB
Last Update: 14/06/2026
Anglo American is a leading global mining company and our products are the essential ingredients in almost every aspect of modern life. Our portfolio of world-class competitive operations, with a broad range of future development options, provides many of the future-ena...
Compliance Ranges Comparison

Sedgman







Anglo American






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Sedgman in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Anglo American in 2026.
Incident History - Sedgman (X = Date, Y = Severity)
Sedgman cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Anglo American (X = Date, Y = Severity)
Anglo American cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sedgman

Anglo American
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.