Comparison Overview
Cisco Meraki

Cisco Meraki
500 Terry A. Francois Blvd, San Francisco, California, US, 94158
Last Update: 21/04/2026
At Cisco Meraki, we create intuitive technologies to optimize experiences, secure locations, and seamlessly connect people, places, and things. We love to push boundaries, experiment, and make IT easier, faster, and smarter for our customers. By doing this, we hope to c...

Workday
6110 Stoneridge Mall Rd, Pleasanton, 94588, US
Last Update: 04/05/2026
By unifying HR and Finance on an open, trusted platform powered by AI, Workday delivers high-impact outcomes our customers can count on. At the heart of our platform is Sana from Workday—the superintelligence that puts AI agents to work for you and your people. Welcome ...
Compliance Ranges Comparison

Cisco Meraki







Workday






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Cisco Meraki has 5.66% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Workday has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Cisco Meraki (X = Date, Y = Severity)
Cisco Meraki cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Workday (X = Date, Y = Severity)
Workday cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Cisco Meraki

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