Comparison Overview
ING Australia
ING Australia
60 Margaret St, Sydney, NSW, 2000, AU
Last Update: 21/12/2025
We exist to empower people to stay ahead, in business and in life. We’re proud to be part of ING Group, the world’s leading direct savings bank – and even prouder to be Australia’s most recommended bank. That’s because, for us, nothing matters more than being loved by o...
Federal Bank
Federal Towers, Head Office, Ernakulam, 683101, IN
Last Update: 01/04/2026
Federal Bank, one of the leading private sector banks with presence across the country, began its journey from humble backgrounds to reach the stature of an institution with national prominence & character. With a rich legacy of 7 decades, the Bank aspires to be the mos...
Compliance Ranges Comparison
ING Australia
Federal Bank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for ING Australia in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Federal Bank in 2026.
Incident History - ING Australia (X = Date, Y = Severity)
ING Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Federal Bank (X = Date, Y = Severity)
Federal Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ING Australia
Federal Bank
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: *.*.