Comparison Overview
Chilean Cement and Concrete Institute

Chilean Cement and Concrete Institute
Avenida Providencia 1208, Providencia, 7500000, CL
Last Update: 02/04/2026
Nuestro Origen El ICH fue creado en 1966 como una corporación privada sin fines de lucro. Sus socios fundadores son la Cámara Chilena de la Construcción, Cementos Bío Bío S.A., Cemento Polpaico S.A. y Lafarge Chile S.A.. Nuestra Misión La misión del ICH es promover...

Kiewit
1550 Mike Fahey St., Omaha, 68102, US
Last Update: 01/04/2026
At Kiewit, the projects we deliver make a difference, and we offer opportunities for you to make one, too. Our construction and engineering professionals work on some of the industry’s most complex, challenging and rewarding projects – whether it’s boring tunnels throug...
Compliance Ranges Comparison

Chilean Cement and Concrete Institute







Kiewit






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Chilean Cement and Concrete Institute in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Kiewit in 2026.
Incident History - Chilean Cement and Concrete Institute (X = Date, Y = Severity)
Chilean Cement and Concrete Institute cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kiewit (X = Date, Y = Severity)
Kiewit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chilean Cement and Concrete Institute

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