Comparison Overview
Eprinsa

Eprinsa
ES
Last Update: 01/04/2026
Empresa pública creada por la Diputación de Córdoba con objeto de dar asistencia informática integral, formación de personal y producción cartográfica a las Administraciones Locales de la provincia: los Ayuntamientos, Diputación, sus Organismos Autónomos, Empresas Públi...

Swiss Federal Administration
Eigerstrasse 71, Bern, 3003, CH
Last Update: 06/08/2026
Seven departments, the Federal Chancellery and around 70 administrative units make up the Federal Administration. With around 38,000 employees, we are one of the largest employers in Switzerland. Everyone who works for the Federal Administration actively contributes t...
Compliance Ranges Comparison

Eprinsa







Swiss Federal Administration






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Eprinsa in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Swiss Federal Administration has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Eprinsa (X = Date, Y = Severity)
Eprinsa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swiss Federal Administration (X = Date, Y = Severity)
Swiss Federal Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Eprinsa

Swiss Federal Administration
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.