Comparison Overview

DraftKings at Casino Queen

VS

Olympia Gaming, L.L.C

DraftKings at Casino Queen

200 S Front St, East St Louis, Illinois, 62201, US
Last Update: 2025-11-27

DraftKings at Casino Queen offers over 980 of the loosest slots in the STL area, best views of the St. Louis skyline, exquisite dining, and local entertainment! Join us at the only Employee Owned Casino in the US! We are also one of the cleanest Casinos and do not allow smoking on the gaming floor, however, we do have a smoker's lounge to accommodate all guests. There's always action in our table games area! Play EZ Baccarat, Ultimate Texas Hold'em, and Three Card Poker. Plus, there's new excitement to our Three Card Poker with 6 Card Bonus! In addition, we have more than 980 of the loosest slots in the area, including Popular progressives, Penny slots, Private high limit area, Video poker games, Favorites like Wonder 4, Lightning Link, Wild Panda and more! DraftKings at Casino Queen also boasts an amazing hotel and RV park with stunning views of the St. Louis Arch and downtown!

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

Olympia Gaming, L.L.C

11411 Southern Highlands Parkway Suite 300, None, Las Vegas, Nevada, US, 89141
Last Update: 2025-11-27
Between 750 and 799

Formed in 2005, Olympia Gaming is the gaming development division of Olympia Companies. Olympia Gaming operates two successful Nevada properties—Casino Fandango in Carson City, and Legends Bay Casino in Sparks. Since 2003, Casino Fandango’s loyal customers have voted it “Best Casino,” “Friendliest Employees,” and more. In 2022, Legends Bay Casino made history as the first Northern Nevada casino to open in more than 20 years.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 16
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/casino-queen-inc..jpeg
DraftKings at Casino Queen
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/olympia-gaming-llc.jpeg
Olympia Gaming, L.L.C
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
DraftKings at Casino Queen
100%
Compliance Rate
0/4 Standards Verified
Olympia Gaming, L.L.C
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 DraftKings at Casino Queen in 2025.

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

No incidents recorded for Olympia Gaming, L.L.C in 2025.

Incident History — DraftKings at Casino Queen (X = Date, Y = Severity)

DraftKings at Casino Queen cyber incidents detection timeline including parent company and subsidiaries

Incident History — Olympia Gaming, L.L.C (X = Date, Y = Severity)

Olympia Gaming, L.L.C cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/casino-queen-inc..jpeg
DraftKings at Casino Queen
Incidents

No Incident

https://images.rankiteo.com/companyimages/olympia-gaming-llc.jpeg
Olympia Gaming, L.L.C
Incidents

No Incident

FAQ

Olympia Gaming, L.L.C company demonstrates a stronger AI Cybersecurity Score compared to DraftKings at Casino Queen company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Olympia Gaming, L.L.C company has disclosed a higher number of cyber incidents compared to DraftKings at Casino Queen company.

In the current year, Olympia Gaming, L.L.C company and DraftKings at Casino Queen company have not reported any cyber incidents.

Neither Olympia Gaming, L.L.C company nor DraftKings at Casino Queen company has reported experiencing a ransomware attack publicly.

Neither Olympia Gaming, L.L.C company nor DraftKings at Casino Queen company has reported experiencing a data breach publicly.

Neither Olympia Gaming, L.L.C company nor DraftKings at Casino Queen company has reported experiencing targeted cyberattacks publicly.

Neither DraftKings at Casino Queen company nor Olympia Gaming, L.L.C company has reported experiencing or disclosing vulnerabilities publicly.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds any compliance certifications.

Neither company holds any compliance certifications.

Neither DraftKings at Casino Queen company nor Olympia Gaming, L.L.C company has publicly disclosed detailed information about the number of their subsidiaries.

DraftKings at Casino Queen company employs more people globally than Olympia Gaming, L.L.C company, reflecting its scale as a Gambling Facilities and Casinos.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds SOC 2 Type 1 certification.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds SOC 2 Type 2 certification.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds ISO 27001 certification.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds PCI DSS certification.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C holds HIPAA certification.

Neither DraftKings at Casino Queen nor Olympia Gaming, L.L.C 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