Comparison Overview
Régie de l’énergie du Canada

Régie de l’énergie du Canada
N/A
Last Update: 28/11/2025
Nous sommes la Régie de l’énergie du Canada. Nous travaillons pour vous afin d’assurer le déplacement sûr de l’énergie partout au Canada. Nous travaillons dans l’intérêt du public. Cela signifie que nous rendons des décisions en fonction de ce qui importe à tous plutôt ...

The Singapore Public Service
Singapore, SG
Last Update: 01/04/2026
The Singapore Public Service works with the elected Government and Singaporeans to forge a common vision of Singapore’s future and bring it into reality. We take pride in living out our values of integrity, service and excellence. Follow us for stories on how our pu...
Compliance Ranges Comparison

Régie de l’énergie du Canada







The Singapore Public Service






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Régie de l’énergie du Canada in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for The Singapore Public Service in 2026.
Incident History - Régie de l’énergie du Canada (X = Date, Y = Severity)
Régie de l’énergie du Canada cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Singapore Public Service (X = Date, Y = Severity)
The Singapore Public Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Régie de l’énergie du Canada

The Singapore Public Service
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.