Comparison Overview
Allianz Reinsurance

Allianz Reinsurance
Königinstraße 28, München, 80802, DE
Last Update: 24/03/2026
Allianz Re is the reinsurance arm of the Allianz Group. Headquartered in Munich, Germany, Allianz Re has offices located close to key markets in Ireland, Singapore, Switzerland and the United States, tailoring reinsurance solutions to the diverse business needs of custo...

HDFC Life
Lodha Excelus, 13th Floor,, Mumbai, 400011, IN
Last Update: 01/04/2026
HDFC Life, one of India’s leading private life insurance companies, offers a range of individual and group insurance solutions. It is a joint venture between Housing Development Finance Corporation Limited (HDFC), India’s leading housing finance institution and abrdn pl...
Compliance Ranges Comparison

Allianz Reinsurance







HDFC Life






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Allianz Reinsurance in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for HDFC Life in 2026.
Incident History - Allianz Reinsurance (X = Date, Y = Severity)
Allianz Reinsurance cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HDFC Life (X = Date, Y = Severity)
HDFC Life cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Allianz Reinsurance

HDFC Life
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: *.*.