Comparison Overview
iSignage Limited
iSignage Limited
55 Hoi Yuen Road, Kwun Tong, Kowloon, HK
Last Update: 12/03/2026
iSignage Limited is the market leader in digital signage solution, at iSignage, we do not simply provide our clients with innovative and powerful solutions, but strive to ensure that they come with maximum user-friendliness to ensure the smoothness of their operations f...
ASGN Incorporated
4400 Cox Road Suite 100, Glen Allen, Virginia, US, 23060
Last Update: 01/04/2026
ASGN Incorporated (NYSE: ASGN) is a leading provider of IT services and solutions across the commercial and government sectors. ASGN helps corporate enterprises and government organizations develop, implement and operate critical IT and business solutions through its in...
Compliance Ranges Comparison
iSignage Limited
ASGN Incorporated
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for iSignage Limited in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for ASGN Incorporated in 2026.
Incident History - iSignage Limited (X = Date, Y = Severity)
iSignage Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ASGN Incorporated (X = Date, Y = Severity)
ASGN Incorporated cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
iSignage Limited
ASGN Incorporated
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: *.*.