Comparison Overview
Howard County Public School System

Howard County Public School System
10910 Clarksville Pike, Ellicott City, 21042, US
Last Update: 04/04/2026
Howard County, Maryland is a suburban community of more than 330,000 situated midway along the Baltimore-Washington corridor. It is a county of contrasts — a blend of old and new, urban and rural, historical and progressive. The county’s borders encompass Ellicott City,...

Cobb County School District
514 Glover Street, Marietta, 30060, US
Last Update: 01/04/2026
The COBB COUNTY SCHOOL DISTRICT is a public school system with administrative offices based at 514 Glover St., Marietta, GA 30060. Cobb County School District (CCSD) is the second largest school system in Georgia. CCSD is responsible for educating more than 112,000 stud...
Compliance Ranges Comparison

Howard County Public School System







Cobb County School District






Benchmark & Cyber Underwriting Signals
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Howard County Public School System in 2026.
Incidents vs Primary and Secondary Education Industry Avg (This Year)
No incidents recorded for Cobb County School District in 2026.
Incident History - Howard County Public School System (X = Date, Y = Severity)
Howard County Public School System cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cobb County School District (X = Date, Y = Severity)
Cobb County School District cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Howard County Public School System

Cobb County School District
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.