Comparison Overview
Sonitor

Sonitor
Drammensveien 288, NO-0238 OSLO, NO
Last Update: 31/07/2026
Sonitor® transforms real-time movement into actionable intelligence, empowering hospitals and clinics to operate smarter, safer, and more efficiently. Purpose-built for healthcare, Sonitor’s solutions help hospitals and health systems improve safety, streamline operat...

Trinity Health
20555 Victor Parkway, Livonia, MI, US, 48152
Last Update: 04/04/2026
Trinity Health is one of the largest not-for-profit, Catholic health care systems in the nation. It is a family of 123,000 colleagues and nearly 27,000 physicians and clinicians caring for diverse communities across 26 states. Nationally recognized for care and experien...
Compliance Ranges Comparison

Sonitor







Trinity Health






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Sonitor has 27.54% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Trinity Health has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sonitor (X = Date, Y = Severity)
Sonitor cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Trinity Health (X = Date, Y = Severity)
Trinity Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sonitor

Trinity Health
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.