Comparison Overview
Mining and Energy Northern Territory

Mining and Energy Northern Territory
76 Esplanade, Darwin City, 0800, AU
Last Update: 07/03/2026
We are refocusing this page to share important Mining and Energy information, relevant to the Northern Territory. If you’re interested in trade and investment information please follow @investment territory The Territory’s natural gas, energy and mining industries bri...

Assurance Maladie
26, Avenue du Professeur André Lemierre, Paris, 75020, FR
Last Update: 01/04/2026
Travailler à l’Assurance Maladie, c’est donner une nouvelle dimension à votre métier et agir au quotidien pour la protection de notre système de santé. Participez à une grande diversité de projets dans un cadre bienveillant et soyez fier de contribuer à une mission ess...
Compliance Ranges Comparison

Mining and Energy Northern Territory







Assurance Maladie






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Mining and Energy Northern Territory in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Assurance Maladie in 2026.
Incident History - Mining and Energy Northern Territory (X = Date, Y = Severity)
Mining and Energy Northern Territory cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Assurance Maladie (X = Date, Y = Severity)
Assurance Maladie cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mining and Energy Northern Territory

Assurance Maladie
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.