Comparison Overview
Standard Bank Mauritius
Standard Bank Mauritius
Level 9, Tower A, 1 Exchange Square, 72201, MU
Last Update: 02/04/2026
Africa is our home, and we are focused on driving her growth. We are a leading integrated financial services group on the African continent with a heritage of 155 years. We have an on-the-ground presence in 20 countries in sub-Saharan Africa, fit-for-purpose represen...
SBI Card
Infinity Tower, DLF City Phase 2, Gurgaon, 122002, IN
Last Update: 02/04/2026
SBI Card was launched in 1998 with the State Bank of India, India's largest bank, as the majority stakeholder. In March 2020, SBI Card was listed on BSE and NSE. Today, SBI Card is India’s largest pure-play credit card issuer with over 20 million cards in force, as of D...
Compliance Ranges Comparison
Standard Bank Mauritius
SBI Card
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Standard Bank Mauritius in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SBI Card in 2026.
Incident History - Standard Bank Mauritius (X = Date, Y = Severity)
Standard Bank Mauritius cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SBI Card (X = Date, Y = Severity)
SBI Card cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Standard Bank Mauritius
SBI Card
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: *.*.