Comparison Overview
GF Inbursa

GF Inbursa
Av. Insurgentes Sur 3500 Col. Peña Pobre, México D.F., Del. Tlapan, 14060, MX
Last Update: 14/03/2026
En Grupo Financiero Inbursa estamos comprometidos con México, somos un Grupo Financiero que integra el mejor capital humano para cuidar y hacer crecer de la manera más eficaz el patrimonio de nuestros clientes y socios. Ofrecemos la más novedosa y extensa gama de pr...

NN Group
Schenkkade 65, Den Haag, 2595, NL
Last Update: 13/09/2026
NN Group is an international financial services company, active in 10 countries, with a strong presence in a number of European countries and Japan. We are rooted in the Netherlands and have a rich history spanning 180 years. With our 16,000 colleagues, NN Group provid...
Compliance Ranges Comparison

GF Inbursa







NN Group






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

GF Inbursa

NN Group
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.