Comparison Overview
Inspection Générale de La Banque Postale

Inspection Générale de La Banque Postale
112, Avenue Émile Zola, Paris, Île-de-France, FR, 75015
Last Update: 12/03/2026
Au cœur du dispositif de contrôle interne du Groupe La Banque Postale, l'Inspection Générale : - Prend en charge le contrôle périodique par des missions d'audit interne, - Est garante de l'évaluation de la maîtrise des risques, - Participe à la constante amé...

Desjardins
100, rue des Commandeurs, Lévis, G6V 7N5, CA
Last Update: 11/09/2026
Desjardins Group is the largest cooperative financial group in North America and the fifth largest cooperative financial group in the world, with assets of $435.8 billion as at March 31, 2024. It was named one of Canada's Best Employers by Forbes magazine and by Mediaco...
Compliance Ranges Comparison

Inspection Générale de La Banque Postale







Desjardins






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Inspection Générale de La Banque Postale in 2026.
Incidents vs Banking Industry Avg (This Year)
Desjardins has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Inspection Générale de La Banque Postale (X = Date, Y = Severity)
Inspection Générale de La Banque Postale cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Desjardins (X = Date, Y = Severity)
Desjardins cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Inspection Générale de La Banque Postale

Desjardins
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.