Comparison Overview
Jacobsen Construction

Jacobsen Construction
5181 W. Amelia Earhart Drive, Salt Lake City, Utah, US, 84116
Last Update: 01/04/2026
Located in Salt Lake City, Utah, Jacobsen Construction is ranked as one of the nation's top general contractors specializing in healthcare, higher education, commercial, civic, technology, historic renovation, and religious projects. As an employee-owned company, we’re ...

Kier Group
Cavendish Place, UK, GB
Last Update: 01/04/2026
Our purpose is to sustainably deliver infrastructure which is vital to the UK. As a leading provider of infrastructure services, construction and property developments, we are committed to delivering for communities and leaving lasting legacies through our work. We are...
Compliance Ranges Comparison

Jacobsen Construction







Kier Group






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

Jacobsen Construction

Kier Group
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.