Comparison Overview
QuestQuanum
QuestQuanum
500 Plaza Drive, Secaucus, 07094, US
Last Update: 29/03/2026
The pursuit of operational excellence requires a more customer-driven approach. It’s never been more important than it is right now to find a technology partner that can help you manage the explosion of healthcare data and convert it to an advantage. You need a partne...
Nova Scotia Health Authority
1276 South Park Street, Halifax, B3H 2Y9, CA
Last Update: 01/04/2026
We are Nova Scotia Health. We are rural and urban. We are in hospitals, health centres and community. We serve individuals and communities from Yarmouth to Cape Breton, from Amherst to Halifax, and everything in between. We are researchers and learners, looking for new...
Compliance Ranges Comparison
QuestQuanum
Nova Scotia Health Authority
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for QuestQuanum in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Nova Scotia Health Authority in 2026.
Incident History - QuestQuanum (X = Date, Y = Severity)
QuestQuanum cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nova Scotia Health Authority (X = Date, Y = Severity)
Nova Scotia Health Authority cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
QuestQuanum
Nova Scotia Health Authority
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: *.*.