Comparison Overview
City of Orange City, Florida

City of Orange City, Florida
205 E Graves Ave, Orange City, 32763, US
Last Update: 30/03/2026
The City of Orange City is proud of its small town ambiance, while offering all the amenities necessary for today’s fast-paced lifestyle. Whether a resident, visitor, or business person, we know you will appreciate all that Orange City has to offer. Orange City is not...

State of Michigan
State Capitol, Lansing, Michigan, US, 48913
Last Update: 01/04/2026
Every day the contributions and achievements of State of Michigan employees have a direct impact on over 10 million Michiganders across the state. If you're looking for a fulfilling career in state government that can make a real difference in the lives of others, you c...
Compliance Ranges Comparison

City of Orange City, Florida







State of Michigan






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Orange City, Florida in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State of Michigan in 2026.
Incident History - City of Orange City, Florida (X = Date, Y = Severity)
City of Orange City, Florida cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Michigan (X = Date, Y = Severity)
State of Michigan cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

City of Orange City, Florida

State of Michigan
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.