Comparison Overview

PENN Entertainment, Inc

VS

Boyd Interactive

PENN Entertainment, Inc

825 Berkshire Blvd., Wyomissing, Pennsylvania, 19610, US
Last Update: 2025-11-21

We have the largest and most diverse gaming footprint in North America. With 43 casinos and racetracks across 20 states, a robust online gaming and sports betting presence and exciting sports media, we’re leading the industry — and pushing it toward the future. Every one of our strategic partnerships helps fuel our community’s growth, their love of gaming — and our continued success as the most innovative omni-channel provider of entertainment experiences.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 8,075
Subsidiaries: 42
12-month incidents
0
Known data breaches
0
Attack type number
0

Boyd Interactive

2235 Sheppard Ave E, 1500, North York, Ontario, CA, M2J 5B5
Last Update: 2025-11-27

Founded in 2013, Pala Interactive envisioned and anticipated the growth of online gaming in the United States. Today, through our Online Gaming Platform, including best-in-class and proprietary technology services, player account management platforms, online casino products and games, combined with relevant content and technological integrations, Pala Interactive is a leader in online real money and social gaming. Pala Interactive operates in multiple States throughout the U.S.A. and Canada within the B2C and B2B space. Pala Interactive was acquired by Boyd Gaming in November of 2022.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 88
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pennnationalgaming.jpeg
PENN Entertainment, Inc
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/boydinteractive.jpeg
Boyd Interactive
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
PENN Entertainment, Inc
100%
Compliance Rate
0/4 Standards Verified
Boyd Interactive
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Gambling Facilities and Casinos Industry Average (This Year)

No incidents recorded for PENN Entertainment, Inc in 2025.

Incidents vs Gambling Facilities and Casinos Industry Average (This Year)

No incidents recorded for Boyd Interactive in 2025.

Incident History — PENN Entertainment, Inc (X = Date, Y = Severity)

PENN Entertainment, Inc cyber incidents detection timeline including parent company and subsidiaries

Incident History — Boyd Interactive (X = Date, Y = Severity)

Boyd Interactive cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pennnationalgaming.jpeg
PENN Entertainment, Inc
Incidents

No Incident

https://images.rankiteo.com/companyimages/boydinteractive.jpeg
Boyd Interactive
Incidents

No Incident

FAQ

PENN Entertainment, Inc company demonstrates a stronger AI Cybersecurity Score compared to Boyd Interactive company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Boyd Interactive company has disclosed a higher number of cyber incidents compared to PENN Entertainment, Inc company.

In the current year, Boyd Interactive company and PENN Entertainment, Inc company have not reported any cyber incidents.

Neither Boyd Interactive company nor PENN Entertainment, Inc company has reported experiencing a ransomware attack publicly.

Neither Boyd Interactive company nor PENN Entertainment, Inc company has reported experiencing a data breach publicly.

Neither Boyd Interactive company nor PENN Entertainment, Inc company has reported experiencing targeted cyberattacks publicly.

Neither PENN Entertainment, Inc company nor Boyd Interactive company has reported experiencing or disclosing vulnerabilities publicly.

Neither PENN Entertainment, Inc nor Boyd Interactive holds any compliance certifications.

Neither company holds any compliance certifications.

PENN Entertainment, Inc company has more subsidiaries worldwide compared to Boyd Interactive company.

PENN Entertainment, Inc company employs more people globally than Boyd Interactive company, reflecting its scale as a Gambling Facilities and Casinos.

Neither PENN Entertainment, Inc nor Boyd Interactive holds SOC 2 Type 1 certification.

Neither PENN Entertainment, Inc nor Boyd Interactive holds SOC 2 Type 2 certification.

Neither PENN Entertainment, Inc nor Boyd Interactive holds ISO 27001 certification.

Neither PENN Entertainment, Inc nor Boyd Interactive holds PCI DSS certification.

Neither PENN Entertainment, Inc nor Boyd Interactive holds HIPAA certification.

Neither PENN Entertainment, Inc nor Boyd Interactive holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H