Comparison Overview
Kroll Brasil

Kroll Brasil
Avenida Jornalista Roberto Marinho 85, São Paulo, 04576-010, BR
Last Update: 27/11/2025
A Kroll é a líder global em gestão de risco, investigações corporativas e assessoria financeira. Há mais de 40 anos ajudamos nossos clientes a tomar decisões sobre pessoas, bens, operações e segurança. O QUE FAZEMOS Somos especializados em identificar, remediar e monit...

Slalom
821 2nd Ave., Suite 1900, Seattle, WA, US, 98104
Last Update: 01/04/2026
Slalom is a fiercely human business and technology consulting company that leads with outcomes to bring more value, in all ways, always. We team with leaders who expect more. So we bring more. From strategy through delivery, our agile teams across 53 offices in 12 coun...
Compliance Ranges Comparison

Kroll Brasil







Slalom






Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Kroll Brasil in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Slalom in 2026.
Incident History - Kroll Brasil (X = Date, Y = Severity)
Kroll Brasil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Slalom (X = Date, Y = Severity)
Slalom cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kroll Brasil

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