Comparison Overview
Risk + Response

Risk + Response
1650 Independence Dr, New Braunfels, 78132, US
Last Update: 16/03/2026
We believe it takes both a highly trained team and cutting-edge technology to create the strongest risk and response methodologies to battle cyber criminals. While we may not outnumber digital bad actors, we will always find ways to outsmart them. Covers topics like #f...

Absa Group
7th Floor, Absa Towers West, 15 Troye Street, Johannesburg, Johannesburg, ZA, 2001
Last Update: 30/06/2026
Absa Group Limited (Absa) has forged a new way of getting things done, driven by bravery and passion, with the readiness to realise growth on the African continent and beyond. We’re a truly African brand, inspired by the people we serve in Botswana, Ghana, Kenya, Maur...
Compliance Ranges Comparison

Risk + Response







Absa Group






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

Risk + Response

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