Comparison Overview

bestbet

VS

Eastside Cannery Casino Hotel

bestbet

201 Monument Rd, Jacksonville, FL, 32225, US
Last Update: 2025-11-27
Between 750 and 799

bestbet features three locations in North Florida and is the state’s top poker, simulcast and gaming operator. The Jacksonville poker room, the largest in Florida, features over 80 tables of all limits, an expansive simulcast wagering facility, and an array of food-and-beverage service that includes sushi. The Orange Park location offers over 30 tables, simulcast wagering, and food-and-beverage service. The St. Augustine location includes 49 tables with a sports bar, sushi bar, and simulcast wagering. The cardrooms are open 24 hours Saturday and Sunday, and from 10am to 4am Monday through Friday. For more information about bestbet, visit http://www.bestbetjax.com.

NAICS: 713
NAICS Definition:
Employees: 179
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Eastside Cannery Casino Hotel

5255 Boulder Highway, Las Vegas, NV, 89122, US
Last Update: 2025-11-27

Conveniently located just off Boulder Highway and only 7 miles from McCarran International Airport, Eastside Cannery Casino & Hotel has become the favorite of area residents for gaming fun, dining value, and star-studded entertainment. With 65,000-square-feet of gaming space, restaurants, and amenities, Eastside Cannery is a world of thrills, delights, and comfort.

NAICS: 713
NAICS Definition:
Employees: 87
Subsidiaries: 25
12-month incidents
0
Known data breaches
6
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bestbet-poker-simulcast-and-racing.jpeg
bestbet
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/eastsidecannery.jpeg
Eastside Cannery Casino Hotel
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
bestbet
100%
Compliance Rate
0/4 Standards Verified
Eastside Cannery Casino Hotel
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 bestbet in 2025.

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

No incidents recorded for Eastside Cannery Casino Hotel in 2025.

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

bestbet cyber incidents detection timeline including parent company and subsidiaries

Incident History — Eastside Cannery Casino Hotel (X = Date, Y = Severity)

Eastside Cannery Casino Hotel cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bestbet-poker-simulcast-and-racing.jpeg
bestbet
Incidents

No Incident

https://images.rankiteo.com/companyimages/eastsidecannery.jpeg
Eastside Cannery Casino Hotel
Incidents

Date Detected: 10/2025
Type:Breach
Blog: Blog

Date Detected: 9/2025
Type:Breach
Blog: Blog

Date Detected: 9/2025
Type:Breach
Motivation: Data Theft, Potential Financial Gain, Fraud/Identity Theft
Blog: Blog

FAQ

Eastside Cannery Casino Hotel company demonstrates a stronger AI Cybersecurity Score compared to bestbet company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Eastside Cannery Casino Hotel company has historically faced a number of disclosed cyber incidents, whereas bestbet company has not reported any.

In the current year, Eastside Cannery Casino Hotel company has reported more cyber incidents than bestbet company.

Neither Eastside Cannery Casino Hotel company nor bestbet company has reported experiencing a ransomware attack publicly.

Eastside Cannery Casino Hotel company has disclosed at least one data breach, while bestbet company has not reported such incidents publicly.

Neither Eastside Cannery Casino Hotel company nor bestbet company has reported experiencing targeted cyberattacks publicly.

Neither bestbet company nor Eastside Cannery Casino Hotel company has reported experiencing or disclosing vulnerabilities publicly.

Neither bestbet nor Eastside Cannery Casino Hotel holds any compliance certifications.

Neither company holds any compliance certifications.

Eastside Cannery Casino Hotel company has more subsidiaries worldwide compared to bestbet company.

bestbet company employs more people globally than Eastside Cannery Casino Hotel company, reflecting its scale as a Gambling Facilities and Casinos.

Neither bestbet nor Eastside Cannery Casino Hotel holds SOC 2 Type 1 certification.

Neither bestbet nor Eastside Cannery Casino Hotel holds SOC 2 Type 2 certification.

Neither bestbet nor Eastside Cannery Casino Hotel holds ISO 27001 certification.

Neither bestbet nor Eastside Cannery Casino Hotel holds PCI DSS certification.

Neither bestbet nor Eastside Cannery Casino Hotel holds HIPAA certification.

Neither bestbet nor Eastside Cannery Casino Hotel 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