Comparison Overview
Sparkasse Duisburg

Sparkasse Duisburg
Königstraße 23 -25, Duisburg, DE, 47051
Last Update: 04/04/2026
Die Sparkasse Duisburg: Modern, leistungsstark, mit 6,62 Mrd. Euro Bilanzsumme (2023) und 1.069 engagierten Mitarbeitern. Wir bieten direkten Kundenkontakt über zahlreiche Geschäftsstellen und moderne Kommunikationsmittel. Als verlässlicher Partner in einer wandelnden R...

KeyBank
127 Public Square, Cleveland , Ohio, US, 44114
Last Update: 07/09/2026
At KeyBank we’ve made a promise to our clients that they will always have a champion in us. To deliver on our promise, we’re committed to building a team of engaged employees who do the right thing for our clients and shareholders, and help them achieve financial wellne...
Compliance Ranges Comparison

Sparkasse Duisburg







KeyBank






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

Sparkasse Duisburg

KeyBank
FAQ
Latest Global CVEs
Netskope was notified about a potential gap in Netskope Endpoint DLP (EPDLP) running on Windows systems. Successful exploitation of the gap could potentially allow a privileged user to send a crafted message to the EPDLP process port to trigger an integer overflow, leading to memory corruption. Successful exploitation would require the EPDLP module to be enabled in the client configuration, and that Memory Integrity is disabled. A successful exploit could potentially result in a denial-of-service, arbitrary code execution, or privilege escalation on the local machine.
Netskope was notified of an out-of-bounds heap read affecting the Endpoint DLP (EPDLP) service of the Netskope Client. A local standard user could potentially send a specially crafted message that is not properly validated with a bounds check, likely crashing the kernel driver handler. Successful exploitation could potentially crash the EPDLP service, temporarily interrupting DLP enforcement. A successful exploit could potentially also reveal per-boot memory layout information to unauthorized users.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is vulnerable to a denial of service where a specific functionality on a Db2 server can be disabled by a privileged user under certain conditions.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an attacker with the ability to control or impersonate a DRDA server endpoint to execute arbitrary commands on Db2 clients due to a stack-based buffer overflow that improperly copies user-controlled data into a fixed-size stack buffer without bounds checking.
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 could allow an authenticated user to send a specially crafted request to write arbitrary files on the system.