Comparison Overview
KFC South Pacific (Yum! Brands Subsidiary)

KFC South Pacific (Yum! Brands Subsidiary)
Frenchs Forest, Sydney, 2086, AU
Last Update: 07/03/2026
Take one man with a big idea, add 11 herbs and spices, grit, ambition and buckets of heart – you’ve got KFC. Since 1952, we’ve been bringing finger lickin’ good chicken to the world. But without our people, The Originals, none of it would be possible. Everyone at KFC is...

GRSA
Rua Werner Von Siemens 111, São Paulo, SP, BR, 05069-010
Last Update: 31/03/2026
GRSA - Soluções em Alimentação e em Serviços de Suporte Oferecer soluções de alimentação saudáveis e equilibradas, com os mais altos padrões de qualidade e de Acordo com as necessidades de cada cliente. Estamos presentes em empresas, escolas, hospitais, terminais...
Compliance Ranges Comparison

KFC South Pacific (Yum! Brands Subsidiary)







GRSA






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for KFC South Pacific (Yum! Brands Subsidiary) in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for GRSA in 2026.
Incident History - KFC South Pacific (Yum! Brands Subsidiary) (X = Date, Y = Severity)
KFC South Pacific (Yum! Brands Subsidiary) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GRSA (X = Date, Y = Severity)
GRSA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

KFC South Pacific (Yum! Brands Subsidiary)

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