Comparison Overview
Natural Sciences and Engineering Research Council of Canada (NSERC)

Natural Sciences and Engineering Research Council of Canada (NSERC)
125 Zaida Eddy Private, Ottawa, K1R 0E3, CA
Last Update: 03/04/2026
NSERC invests over $1 billion each year in natural sciences and engineering research in Canada. Our investments deliver discoveries, valuable world-firsts in knowledge claimed by a brain trust of over 11,000 professors, world-leading researchers in their fields. Our i...

FDA
10903 New Hampshire Ave, Silver Spring, 20993, US
Last Update: 02/04/2026
The Food and Drug Administration is an agency within the Department of Health and Human Services. The FDA is responsible for protecting the public health by ensuring the safety, efficacy, and security of human and veterinary drugs, biological products, and medical devi...
Compliance Ranges Comparison

Natural Sciences and Engineering Research Council of Canada (NSERC)







FDA






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Natural Sciences and Engineering Research Council of Canada (NSERC) in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for FDA in 2026.
Incident History - Natural Sciences and Engineering Research Council of Canada (NSERC) (X = Date, Y = Severity)
Natural Sciences and Engineering Research Council of Canada (NSERC) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FDA (X = Date, Y = Severity)
FDA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Natural Sciences and Engineering Research Council of Canada (NSERC)

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