Comparison Overview
Koch Minerals & Trading

Koch Minerals & Trading
4111 E 37th St N, Wichita, Kansas, 67220, US
Last Update: 11/03/2026
At KM&T, we focus on the real-time trading of real-world resources to create real, long-term value that makes life better for people all over the world. We specialize in the innovative procurement, exchange and delivery of essential commodity products and services that ...

Transocean
Turmstrasse 30, Zug, 0000, CH
Last Update: 02/04/2026
Transocean is a leading international provider of offshore contract drilling services for oil and gas wells. The company specializes in technically demanding sectors of the global offshore drilling business, with a particular focus on ultra-deepwater and harsh environme...
Compliance Ranges Comparison

Koch Minerals & Trading







Transocean






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Koch Minerals & Trading in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Transocean in 2026.
Incident History - Koch Minerals & Trading (X = Date, Y = Severity)
Koch Minerals & Trading cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Transocean (X = Date, Y = Severity)
Transocean cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Koch Minerals & Trading

Transocean
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.