Comparison Overview
Prudential

Prudential
Newark, 07043
Last Update: 05/03/2026
We solve Investment, Insurance and Retirement challenges, helping individuals, organizations and communities reach their goals. (Pru.us/disclaimer)

Lloyds Banking Group
25 Gresham Street, London, EC2V 7HN, GB
Last Update: 02/08/2026
Our purpose is Helping Britain Prosper. We do this by creating a more sustainable and inclusive future for people and businesses, shaping finance as a force for good. We're part of an ever-changing industry and are currently on a journey to shape the financial services...
Compliance Ranges Comparison

Prudential







Lloyds Banking Group






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Prudential in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Lloyds Banking Group has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Prudential (X = Date, Y = Severity)
Prudential cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lloyds Banking Group (X = Date, Y = Severity)
Lloyds Banking Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prudential

Lloyds Banking 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.