Comparison Overview
Emirates NBD KSA

Emirates NBD KSA
8152 King Fahd Road, Al Muhammadiyah, 12363, SA
Last Update: 03/04/2026
Emirates NBD – KSA was established in 2004 as the first UAE-based bank in the Kingdom of Saudi Arabia and has grown to be one of the Group’s largest banking operations outside the UAE with a fully-fledged range of retail, SME, corporate and treasury services targeting v...

Global Payments Inc.
Atlanta, Georgia, US
Last Update: 05/10/2026
Global Payments (NYSE: GPN) is a leading payment technology and software company that powers commerce for businesses of all sizes worldwide. We help businesses grow with confidence by delivering innovative solutions that enable seamless payment acceptance, smarter opera...
Compliance Ranges Comparison

Emirates NBD KSA







Global Payments Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Emirates NBD KSA in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Global Payments Inc. in 2026.
Incident History - Emirates NBD KSA (X = Date, Y = Severity)
Emirates NBD KSA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Global Payments Inc. (X = Date, Y = Severity)
Global Payments Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Emirates NBD KSA

Global Payments Inc.
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.