Comparison Overview

Seminole Nation Gaming Enterprise

VS

Metropolitan Gaming

Seminole Nation Gaming Enterprise

11277 Hwy 99, Seminole, 74868, US
Last Update: 2025-11-27

Seminole Nation Gaming Enterprise (SNGE) is an entity of the Seminole Nation of Oklahoma. We proudly operate three casinos within the Seminole Nation of Oklahoma territory, Seminole Nation Casino, Wewoka Trading Post Casino and River Mist Casino. We offer Class II and Class III games for your gaming pleasure. SNGE is continuously focusing on improving the gaming experience and excitement for our patrons. We welcome friends to visit our facilities where Winning Is FUN!

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

Metropolitan Gaming

Fourth floor, 265 Tottenham Court Road, Bloomsbury, London, England, W1T 7RQ, GB
Last Update: 2025-11-27

Metropolitan Gaming brands in in the UK include the Metropolitan Casino in Mayfair, Empire Casino, The Sportsman, Park Lane Club London, The Rendezvous (Brighton), Manchester235, and Alea Casinos (Nottingham and Glasgow). International properties include three casinos in Egypt. The Metropolitan portfolio also includes celebrity chef restaurants by James Martin and Marco Pierre White, and a sports bar in partnership with Budweiser.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/seminole-nation-gaming-enterprise.jpeg
Seminole Nation Gaming Enterprise
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/caesars-entertainment-emea.jpeg
Metropolitan Gaming
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
Seminole Nation Gaming Enterprise
100%
Compliance Rate
0/4 Standards Verified
Metropolitan Gaming
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 Seminole Nation Gaming Enterprise in 2025.

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

No incidents recorded for Metropolitan Gaming in 2025.

Incident History — Seminole Nation Gaming Enterprise (X = Date, Y = Severity)

Seminole Nation Gaming Enterprise cyber incidents detection timeline including parent company and subsidiaries

Incident History — Metropolitan Gaming (X = Date, Y = Severity)

Metropolitan Gaming cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seminole-nation-gaming-enterprise.jpeg
Seminole Nation Gaming Enterprise
Incidents

No Incident

https://images.rankiteo.com/companyimages/caesars-entertainment-emea.jpeg
Metropolitan Gaming
Incidents

No Incident

FAQ

Metropolitan Gaming company demonstrates a stronger AI Cybersecurity Score compared to Seminole Nation Gaming Enterprise company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Metropolitan Gaming company has disclosed a higher number of cyber incidents compared to Seminole Nation Gaming Enterprise company.

In the current year, Metropolitan Gaming company and Seminole Nation Gaming Enterprise company have not reported any cyber incidents.

Neither Metropolitan Gaming company nor Seminole Nation Gaming Enterprise company has reported experiencing a ransomware attack publicly.

Neither Metropolitan Gaming company nor Seminole Nation Gaming Enterprise company has reported experiencing a data breach publicly.

Neither Metropolitan Gaming company nor Seminole Nation Gaming Enterprise company has reported experiencing targeted cyberattacks publicly.

Neither Seminole Nation Gaming Enterprise company nor Metropolitan Gaming company has reported experiencing or disclosing vulnerabilities publicly.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds any compliance certifications.

Neither company holds any compliance certifications.

Metropolitan Gaming company has more subsidiaries worldwide compared to Seminole Nation Gaming Enterprise company.

Metropolitan Gaming company employs more people globally than Seminole Nation Gaming Enterprise company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds SOC 2 Type 1 certification.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds SOC 2 Type 2 certification.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds ISO 27001 certification.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds PCI DSS certification.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming holds HIPAA certification.

Neither Seminole Nation Gaming Enterprise nor Metropolitan Gaming 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