Comparison Overview
Sparkasse Hochsauerland

Sparkasse Hochsauerland
Am Markt 4, Brilon, 59929, DE
Last Update: 03/04/2026
Wir sind eine leistungsstarke und vertriebsorientierte Sparkasse im östlichen Hochsauerland mit einer Bilanzsumme von rund 1,5 Mrd. Euro. Nähe und Kompetenz zählen in 8 Filialen zu unseren zentralen Erfolgsfaktoren. Als regional verankertes Kreditinstitut sind wir ein b...

Westpac
Head Office: 200 Barangaroo Avenue, Sydney, 2000, AU
Last Update: 14/09/2026
To turn doing into done, it takes a little Westpac. From rescue helicopters and signing the Equator Principles, to paying super during parental leave and initiatives like Westpac SaferPay and SafeCall that help protect customers from scams... we have a proud history of...
Compliance Ranges Comparison

Sparkasse Hochsauerland







Westpac






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

Sparkasse Hochsauerland

Westpac
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.