Comparison Overview
Anne Arundel County Department of Health

Anne Arundel County Department of Health
N/A
Last Update: 03/04/2026
The Department of Health, established October 1930, is the sole government agency responsible for improving the health of Anne Arundel County. By State and County authority, the Department of Health is charged with enforcement of certain federal, State and County laws a...

Johnson & Johnson
New Brunswick, NJ, US, 08903
Last Update: 28/06/2026
At Johnson & Johnson, we believe health is everything. Our strength in healthcare innovation empowers us to build a world where complex diseases are prevented, treated, and cured, where treatments are smarter and less invasive, and solutions are personal. Through our ex...
Compliance Ranges Comparison

Anne Arundel County Department of Health







Johnson & Johnson






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Anne Arundel County Department of Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Johnson & Johnson has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Anne Arundel County Department of Health (X = Date, Y = Severity)
Anne Arundel County Department of Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson & Johnson (X = Date, Y = Severity)
Johnson & Johnson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Anne Arundel County Department of Health

Johnson & Johnson
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.