Skip to main content

Security report for yum.com

Yum! Brands, Inc. · Hospitality · United States

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

73/100

Risk levelMedium

0–100, higher is better. How it is calculated

Yum! Brands, Inc. is a leading global quick-service restaurant company operating iconic brands such as KFC, Pizza Hut, and Taco Bell. The company targets consumers worldwide, franchisees, investors, and job seekers, operating primarily through franchising and company-operated stores. The website reflects Yum! Brands' enterprise scale and market leadership with professional branding and comprehensive content. Technically, the site leverages modern frameworks including Dojo Toolkit, Bootstrap, and Google Tag Manager, hosted on IBM WebSphere Portal, providing a solid digital infrastructure with good mobile optimization and accessibility. Security posture is strong with HTTPS enforcement, security headers, and cookie consent mechanisms, though explicit security policy and incident response information are not prominently published. The absence of WHOIS data is notable but does not detract from the site's legitimacy given the brand's global presence and professional web presence. Overall, the site is trustworthy, well-maintained, and compliant with privacy regulations.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching yum.com

This scan found 18 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
52
Security headers
35
Email security
80
DNS health
85
Network security
100
GDPR outside view
88
Average
73

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Yum! Brands holds a dominant position in the quick-service restaurant industry with a diversified portfolio of globally recognized brands. Its business model focuses on franchising, enabling rapid expansion and revenue generation through royalties and brand management. The company targets a broad consumer base and maintains strong investor relations. The website's content and linked domains reinforce its brand ecosystem. The company demonstrates a mature partnership network and a strategic focus on digital engagement and compliance. Growth indicators include active social media presence and comprehensive corporate communications. The lack of visible security policy and incident response pages suggests an opportunity for enhanced transparency.

Security posture

The website exhibits a mature security posture with enforced HTTPS, multiple security headers, and a cookie consent mechanism aligned with GDPR compliance. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. However, the absence of a dedicated security policy page and incident response contact information limits transparency and may impact stakeholder confidence. The site does not publish a vulnerability disclosure program or security.txt file, which are best practices for modern corporate websites. Overall, the security measures are robust but could be improved by adding explicit security governance documentation and incident response channels.

Recommendations

  1. Publish a dedicated security policy page outlining security governance and practices.
  2. Provide clear incident response contact information, including security@ or abuse@ email addresses.
  3. Implement and publicize a vulnerability disclosure program or security.txt file.
  4. Enhance transparency by publishing data protection officer contact details.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
Yum! Brands, Inc.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Yum! Brands, Inc.
Description
Yum! Brands is a global leader in the quick-service restaurant industry, operating well-known brands including KFC, Pizza Hut, and Taco Bell.
Key services
Restaurant franchising, Brand management, Food service
Content quality
excellent
Branding
consistent

Technology

Stack
Dojo Toolkit 1.9, jQuery 3.5.1, Bootstrap 5.0.2, Google Tag Manager, OneTrust Cookie Consent
Frameworks
Dojo, Bootstrap
Platforms
WebSphere Portal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of security headers

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
OneTrust Cookie Consent
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Content is comprehensive and professionally presented.
  3. Strong privacy and cookie consent mechanisms are in place.
  4. WHOIS data is unavailable, which is unusual for a major brand domain.
  5. No security policy or incident response pages explicitly found.
  6. Use of modern web technologies and frameworks.
  7. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on IBM WebSphere Portal using Dojo Toolkit 1.9, Bootstrap 5.0.2, and jQuery 3.5.1, indicating a mature and enterprise-grade technology stack. Google Tag Manager is used for analytics and marketing tracking, and OneTrust manages cookie consent, reflecting compliance with privacy regulations. The site demonstrates good mobile responsiveness and accessibility features. Performance is moderate, likely due to the complexity of the portal framework and multiple external dependencies. The site uses modern CSS and JavaScript practices, but there is room for optimization to improve load times. No CMS other than WebSphere Portal was detected. Hosting provider details are not explicit but likely enterprise-grade. Overall, the technical infrastructure supports the business needs effectively with opportunities for performance tuning.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with yum.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review yum.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.