Comparison Overview
belairdirect
belairdirect
7101, rue Jean-Talon Est, Anjou, undefined, H1M 3T6, CA
Last Update: 27/02/2026
Insurance is too important to be complicated. That’s why we’ve been simplifying it for over 65 years. With offices in six cities across the country, our 1,600 employees help Canadians protect the things they care about by offering a personalized experience where they ca...
Axis Max Life Insurance Limited
11th Floor, DLF Square Building, Jacaranda Marg, DLF City Phase II, Gurugram, Haryana, IN, 122002
Last Update: 01/04/2026
Axis Max Life Insurance Limited (earlier known as Max Life Insurance Company Limited) is a Joint Venture between Max Financial Services Limited and Axis Bank Limited. Max Financial Services Ltd. is a part of the Max Group, an Indian multi-business corporation. Axis Max...
Compliance Ranges Comparison
belairdirect
Axis Max Life Insurance Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for belairdirect in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Axis Max Life Insurance Limited in 2026.
Incident History - belairdirect (X = Date, Y = Severity)
belairdirect cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Axis Max Life Insurance Limited (X = Date, Y = Severity)
Axis Max Life Insurance Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
belairdirect
Axis Max Life Insurance Limited
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: *.*.