Comparison Overview
State Secretariat for Migration SEM, Switzerland
State Secretariat for Migration SEM, Switzerland
Quellenweg 6, Bern-Wabern, BE, 3003, CH
Last Update: 04/12/2025
Das Staatssekretariat regelt, unter welchen Bedingungen jemand in die Schweiz einreisen, hier leben und arbeiten darf – und es entscheidet, wer hier Schutz vor Verfolgung erhält. Gemeinsam mit den Kantonen organisiert das Staatssekretariat die Unterbringung der Asylsuch...
DNV
Veritasveien 1, Høvik, Oslo, NO, 1322
Last Update: 02/04/2026
DNV is the independent expert in risk management and assurance, operating in more than 100 countries. Through its broad experience and deep expertise DNV advances safety and sustainable performance, sets industry benchmarks, and inspires and invents solutions. Whether...
Compliance Ranges Comparison
State Secretariat for Migration SEM, Switzerland
DNV
Benchmark & Cyber Underwriting Signals
Incidents vs Public Safety Industry Avg (This Year)
No incidents recorded for State Secretariat for Migration SEM, Switzerland in 2026.
Incidents vs Public Safety Industry Avg (This Year)
No incidents recorded for DNV in 2026.
Incident History - State Secretariat for Migration SEM, Switzerland (X = Date, Y = Severity)
State Secretariat for Migration SEM, Switzerland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DNV (X = Date, Y = Severity)
DNV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
State Secretariat for Migration SEM, Switzerland
DNV
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.