Comparison Overview
Aditya Birla Sun Life Insurance
Aditya Birla Sun Life Insurance
One World Centre Tower 1, 16th Floor, Jupiter Mill Compound, 841, Senapati Bapat Marg Marg, Elphinstone Road, Mumbai, 400013, IN
Last Update: 01/04/2026
Established in 2000, Aditya Birla Sun Life Insurance Company Limited (formerly Birla Sun Life Insurance Company Limited) is a joint venture between the Aditya Birla Group, a well known and trusted name globally amongst Indian conglomerates and Sun Life Financial Inc, le...
Groupama
8-10 rue d'astorg, Paris, 75008, FR
Last Update: 03/04/2026
« Etre là pour les autres, j'ai décidé d'en faire mon métier. » Portée par nos 32 000 collaborateurs, notre campagne de communication employeur souligne ce qui nous rassemble et nous rend fiers au quotidien : notre métier, le point de départ de belles histoires, humain...
Compliance Ranges Comparison
Aditya Birla Sun Life Insurance
Groupama
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Aditya Birla Sun Life Insurance in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Groupama in 2026.
Incident History - Aditya Birla Sun Life Insurance (X = Date, Y = Severity)
Aditya Birla Sun Life Insurance cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Groupama (X = Date, Y = Severity)
Groupama cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Aditya Birla Sun Life Insurance
Groupama
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: *.*.