Comparison Overview
Avigilon

Avigilon
555 Robson Street, Vancouver, BC, V6B 3K9, CA
Last Update: 07/03/2026
Avigilon was acquired by Motorola Solutions in 2018 and is now part of its ecosystem of safety and security technologies. Avigilon's security suite provides a comprehensive portfolio of end-to-end video security products and services that is part of Motorola Solutions...

Securitas Nederland
De Corridor 3a, Breukelen, Utrecht, NL, 3621
Last Update: 01/04/2026
Door de juiste inzet van mens, kennis en techniek vinden we de ideale ‘veiligheidsbalans’ voor iedere situatie. Dat begint altijd met heel goed luisteren om zo te doorgronden wat de specifieke omstandigheden en wensen van de klant zijn. Vervolgens groeien we samen naar ...
Compliance Ranges Comparison

Avigilon







Securitas Nederland






Benchmark & Cyber Underwriting Signals
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Avigilon in 2026.
Incidents vs Security and Investigations Industry Avg (This Year)
No incidents recorded for Securitas Nederland in 2026.
Incident History - Avigilon (X = Date, Y = Severity)
Avigilon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Securitas Nederland (X = Date, Y = Severity)
Securitas Nederland cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Avigilon

Securitas Nederland
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.