Comparison Overview
Defra digital, data, technology and security

Defra digital, data, technology and security
England, GB
Last Update: 26/02/2026
We are the trusted teams for developing and delivering digital, data, technology and security solutions across the entire Defra group of organisations. We have around 1,200 colleagues, including programme and project managers, digital developers, data analysts, user re...

NCS Group
Singapore, 5 Ang Mo Kio Street 62, NCS Hub, Singapore, SG, 569141
Last Update: 01/04/2026
NCS, a subsidiary of Singtel Group, is a leading technology services firm with presence in Asia Pacific and partners with governments and enterprises to advance communities through technology. Combining the experience and expertise of its 14,000-strong team across 56 sp...
Compliance Ranges Comparison

Defra digital, data, technology and security







NCS Group






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Defra digital, data, technology and security in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NCS Group in 2026.
Incident History - Defra digital, data, technology and security (X = Date, Y = Severity)
Defra digital, data, technology and security cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NCS Group (X = Date, Y = Severity)
NCS Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Defra digital, data, technology and security

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