Comparison Overview
AQD by Comply365

AQD by Comply365
Wellington, NZ
Last Update: 29/11/2025
AQD by Comply365 specialise in safety and risk management, working alongside highly regulated industries who keep people, products and information moving. Designed to capture vital safety, compliance and risk data in a consistent and connected way, AQD supports you to c...

Databricks
160 Spear Street, 13th Floor, San Francisco, CA, US, 94105
Last Update: 01/04/2026
Databricks is the Data and AI company. More than 20,000 organizations worldwide — including adidas, AT&T, Bayer, Block, Mastercard, Rivian, Unilever, and over 60% of the Fortune 500 — rely on Databricks to build and scale data and AI apps, analytics and agents. Headquar...
Compliance Ranges Comparison

AQD by Comply365







Databricks






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for AQD by Comply365 in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Databricks in 2026.
Incident History - AQD by Comply365 (X = Date, Y = Severity)
AQD by Comply365 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Databricks (X = Date, Y = Severity)
Databricks cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AQD by Comply365

Databricks
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.