Comparison Overview
U.S. Embassy Dar es Salaam

U.S. Embassy Dar es Salaam
686 Old Bagamoyo Road, Msasani, 1, TZ
Last Update: 24/02/2026
Official account of the U.S. Ambassador to Tanzania. For Twitter follow me on https://twitter.com/USAmbTanzania. Terms of Use of this and other social media platforms are available at: https://www.state.gov/tou

Australian Public Service
Canberra, AU
Last Update: 28/03/2026
The work of the Australian Public Service (APS) touches almost every part of Australian life. We provide policy advice to the Australian government on everything from national health to foreign policy. Work towards something greater than yourself. The Australian Publi...
Compliance Ranges Comparison

U.S. Embassy Dar es Salaam







Australian Public Service






Benchmark & Cyber Underwriting Signals
Incidents vs Government Relations Services Industry Avg (This Year)
No incidents recorded for U.S. Embassy Dar es Salaam in 2026.
Incidents vs Government Relations Services Industry Avg (This Year)
No incidents recorded for Australian Public Service in 2026.
Incident History - U.S. Embassy Dar es Salaam (X = Date, Y = Severity)
U.S. Embassy Dar es Salaam cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Australian Public Service (X = Date, Y = Severity)
Australian Public Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Embassy Dar es Salaam

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