Comparison Overview
Scottish Widows Workplace Pensions

Scottish Widows Workplace Pensions
London, City of London, GB
Last Update: 19/02/2026
At Scottish Widows, we build long term relationships with employers and our relationship-led service teams can help employers and their employees; from setting up schemes to supporting the on-going management of workplace pension schemes. We can provide contract-based ...

Northern Trust
50 S. La Salle, Chicago, Illinois, US, 60603
Last Update: 02/04/2026
As a global leader in innovative wealth management, asset servicing and investment solutions, Northern Trust (Nasdaq: NTRS) is proud to guide the world’s most successful individuals, families and institutions by remaining true to our enduring principles of service, expe...
Compliance Ranges Comparison

Scottish Widows Workplace Pensions







Northern Trust






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Scottish Widows Workplace Pensions in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Northern Trust in 2026.
Incident History - Scottish Widows Workplace Pensions (X = Date, Y = Severity)
Scottish Widows Workplace Pensions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Northern Trust (X = Date, Y = Severity)
Northern Trust cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Scottish Widows Workplace Pensions

Northern Trust
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.