Comparison Overview
Inicea

Inicea
21-25, Rue Balzac, Paris, 75008, FR
Last Update: 31/01/2026
Experts et engagés pour votre santé. Inicea regroupe l’ensemble des activités santé de la communauté Clariane en France. Avec plus de 110 cliniques et hôpitaux de jour répartis sur tout le territoire français, Inicea revendique une approche innovante du parcours de soin...

UNC Health
101 Manning Drive, Chapel Hill, North Carolina, US, 27516
Last Update: 01/04/2026
Our mission is to improve the health and well-being of North Carolinians and others whom we serve. We accomplish this by providing leadership and excellence in the interrelated areas of patient care, education and research. UNC Health and its 40,000 teammates, continue...
Compliance Ranges Comparison

Inicea







UNC Health






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Inicea in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UNC Health in 2026.
Incident History - Inicea (X = Date, Y = Severity)
Inicea cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UNC Health (X = Date, Y = Severity)
UNC Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Inicea

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