Comparison Overview
BankSA

BankSA
97 King William Street, Adelaide, South Australia, 5000, AU
Last Update: 25/12/2025
BankSA has been part of the fabric of South Australia since 1848, when The Savings Bank of South Australia began its life as a small one-person outfit. From the past to the future, we’re committed to backing the state. That’s why we back SA. It’s our commitment to the ...

alrajhi bank
King Fahad Branch Road, Al Rajhi Tower, Riyadh, Riyadh Province, SA, 11411
Last Update: 04/05/2026
Founded in 1957, Al Rajhi Bank is one of the largest Islamic banks in the world with total assets of SR 384 billion (US$ 102 billion), a paid up capital of SR 25 billion (US$ 6.66 billion) and an employee base of over 9,600 associates. With over 58 years of experience i...
Compliance Ranges Comparison

BankSA







alrajhi bank






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

BankSA

alrajhi bank
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.