Comparison Overview
Intesa Sanpaolo
Intesa Sanpaolo
Piazza San Carlo 156, Turin, TO, IT, 10121
Last Update: 02/04/2026
Intesa Sanpaolo è il maggior gruppo bancario in Italia con una significativa presenza internazionale. Il suo business model distintivo la rende leader a livello europeo nel Wealth Management, Protection & Advisory e ne caratterizza l’orientamento al digitale. I’impegno ...
ABN AMRO Bank N.V.
Gustav Mahlerlaan 10, Amsterdam, NL, 1082PP
Last Update: 02/04/2026
Welkom op het LinkedIn-account van ABN AMRO. We staan 24/7 klaar om jouw vragen te beantwoorden. Onze taak is altijd om de klant te ondersteunen op het moment dat het er echt op aankomt. Dat is onze verantwoordelijkheid. Dat maakt ons relevant. En wat er vandaag de dag...
Compliance Ranges Comparison
Intesa Sanpaolo
ABN AMRO Bank N.V.
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
Intesa Sanpaolo has 44.13% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ABN AMRO Bank N.V. in 2026.
Incident History - Intesa Sanpaolo (X = Date, Y = Severity)
Intesa Sanpaolo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ABN AMRO Bank N.V. (X = Date, Y = Severity)
ABN AMRO Bank N.V. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Intesa Sanpaolo
ABN AMRO Bank N.V.
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.