Comparison Overview
Hikvision Thailand
Hikvision Thailand
202 อาคารเลอคองคอร์ด, ถนนรัชดาภิเษก เขตห้วยขวาง, กรุงเทพมหานคร, 10310, TH
Last Update: 15/02/2026
Hikvision เป็นผู้ให้บริการโซลูชัน IoT ชั้นนำของโลก โดยมีกล้องวงจรปิดเป็นผลิตภัณฑ์หลัก ปัจจุบัน Hikvision มีพนักงานมากกว่า 40,000 คนมีวิศวกรวิจัยและพัฒนากว่า 19,000 คน เราลงทุนมากกว่า 8% ของยอดขายต่อปีเพื่อการวิจัยและพัฒนานวัตกรรมผลิตภัณฑ์อย่างต่อเนื่อง Hikvision ได้จัดต...
GardaWorld
2300 Émile-Bélanger, Saint-Laurent , H4R 3J4, CA
Last Update: 01/04/2026
GardaWorld is the world’s largest privately-owned security services company, offering cash services, physical and specialized security solutions, and with our Crisis24 portal, the dissemination of verified information related to international security. GardaWorld est ...
Compliance Ranges Comparison
Hikvision Thailand
GardaWorld
Benchmark & Cyber Underwriting Signals
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Hikvision Thailand in 2026.
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for GardaWorld in 2026.
Incident History - Hikvision Thailand (X = Date, Y = Severity)
Hikvision Thailand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GardaWorld (X = Date, Y = Severity)
GardaWorld cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hikvision Thailand
GardaWorld
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: *.*.