Comparison Overview

Pinnacle

VS

MGM National Harbor

Pinnacle

undefined, Willemstad, undefined, undefined, CW
Last Update: 2025-11-27
Between 750 and 799

Pinnacle (formerly known as Pinnacle Sports) was established in 1998, and since that time has been offering bettors a unique alternative to other bookmakers. Our gimmick free approach simply focuses on offering the best odds, and highest betting limits for every market we provide, so bettors win more compared to the competition.

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

MGM National Harbor

101 MGM National Ave, National Harbor, Maryland, US, 20745
Last Update: 2025-11-27

Located in an unrivaled setting, MGM National Harbor offers stunning panoramic views of the eastern shore of the Potomac River in Maryland. The $1.4 billion LEED® Gold Certified resort sits a short distance from Washington, D.C. to the north and historic sites, including George Washington’s Mount Vernon estate across the river in Virginia. The 24-story, 308-room resort features premier amenities and experiences for locals as well as visitors from around the world including a dynamic two-level casino with over 160,000 square feet of space that includes slots, table games and poker; a world-class spa and salon; an entertainment theater with flexible seating for up to 3,000; high- end branded retail; 50,000 square feet of meeting space; and restaurants from renowned local, national, and international chefs. MGM National Harbor is owned by MGM Resorts International (NYSE: MGM). Must be 21+. Please play responsibly. For help visit mdgamblinghelp.org or call 1.800.GAMBLER

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/pinnacle-sports.jpeg
Pinnacle
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/mgm-national-harbor.jpeg
MGM National Harbor
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
Pinnacle
100%
Compliance Rate
0/4 Standards Verified
MGM National Harbor
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 Pinnacle in 2025.

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

No incidents recorded for MGM National Harbor in 2025.

Incident History — Pinnacle (X = Date, Y = Severity)

Pinnacle cyber incidents detection timeline including parent company and subsidiaries

Incident History — MGM National Harbor (X = Date, Y = Severity)

MGM National Harbor cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/pinnacle-sports.jpeg
Pinnacle
Incidents

No Incident

https://images.rankiteo.com/companyimages/mgm-national-harbor.jpeg
MGM National Harbor
Incidents

Date Detected: 8/2025
Type:Ransomware
Attack Vector: Social Engineering, Phishing, SIM Swapping, Hypervisor-Level Attacks
Motivation: Financial Gain
Blog: Blog

Date Detected: 7/2025
Type:Cyber Attack
Attack Vector: Ransomware, Swatting, Extortion, DDoS, SIM Swapping, Cryptocurrency Theft
Motivation: Financial Gain, Retaliation, Ideology, Sexual Gratification, Notoriety
Blog: Blog

Date Detected: 7/2025
Type:Breach
Attack Vector: Social Engineering, Help Desk Impersonation
Motivation: Financial
Blog: Blog

FAQ

MGM National Harbor company demonstrates a stronger AI Cybersecurity Score compared to Pinnacle company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

MGM National Harbor company has historically faced a number of disclosed cyber incidents, whereas Pinnacle company has not reported any.

In the current year, MGM National Harbor company has reported more cyber incidents than Pinnacle company.

MGM National Harbor company has confirmed experiencing a ransomware attack, while Pinnacle company has not reported such incidents publicly.

MGM National Harbor company has disclosed at least one data breach, while Pinnacle company has not reported such incidents publicly.

MGM National Harbor company has reported targeted cyberattacks, while Pinnacle company has not reported such incidents publicly.

Neither Pinnacle company nor MGM National Harbor company has reported experiencing or disclosing vulnerabilities publicly.

Neither Pinnacle nor MGM National Harbor holds any compliance certifications.

Neither company holds any compliance certifications.

MGM National Harbor company has more subsidiaries worldwide compared to Pinnacle company.

MGM National Harbor company employs more people globally than Pinnacle company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Pinnacle nor MGM National Harbor holds SOC 2 Type 1 certification.

Neither Pinnacle nor MGM National Harbor holds SOC 2 Type 2 certification.

Neither Pinnacle nor MGM National Harbor holds ISO 27001 certification.

Neither Pinnacle nor MGM National Harbor holds PCI DSS certification.

Neither Pinnacle nor MGM National Harbor holds HIPAA certification.

Neither Pinnacle nor MGM National Harbor 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