Comparison Overview
Hong Leong Assurance Berhad
Hong Leong Assurance Berhad
15A Jalan 51a/219, Petaling Jaya, 46100, MY
Last Update: 27/03/2026
A PIDM Member. Hong Leong Assurance Berhad (HLA) is a subsidiary of HLA Holdings Sdn Bhd (HLAH), which is fully owned by Hong Leong Financial Group Berhad (HLFG), the financial services division of Hong Leong Group Malaysia. HLA started as Malaysia Pacific Insurance Be...
BDO Unibank
7899 Makati Ave, Makati, 0726, PH
Last Update: 01/04/2026
BDO is a full-service universal bank in the Philippines. It provides a complete array of industry-leading products and services including Lending (corporate and consumer), Deposit-taking, Foreign Exchange, Brokering, Trust and Investments, Credit Cards, Corporate Cash M...
Compliance Ranges Comparison
Hong Leong Assurance Berhad
BDO Unibank
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Hong Leong Assurance Berhad in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BDO Unibank in 2026.
Incident History - Hong Leong Assurance Berhad (X = Date, Y = Severity)
Hong Leong Assurance Berhad cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BDO Unibank (X = Date, Y = Severity)
BDO Unibank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hong Leong Assurance Berhad
BDO Unibank
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: *.*.