Comparison Overview

Gaming Capital Group, LLC

VS

Leelanau Sands Casino & Lodge

Gaming Capital Group, LLC

500 NW 32ND STREET, NEWCASTLE, OK, 73065, US
Last Update: 2025-11-27

Gaming Capital Group is a direct, flexible source of capital for the gaming industry. GCG provides equipment financing, as well as a wide array of financial services, to meet any and all gaming industry needs. In doing so, GCG encourages the development of new gaming projects, helps casinos adapt and thrive in an ever-changing financial environment, and supports the varied needs of an economically important and rapidly expanding industry. GCG continues to experience continued and significant growth. To date, GCG has provided over $1 billion of capital for equipment financing, including casino and hotel projects. We are one of the largest customers of gaming manufacturers, having purchased over 22,000 electronic gaming devices. Our customer base has expanded as well, with our team operating within 26 gaming jurisdictions and 128 casinos.

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

Leelanau Sands Casino & Lodge

2521 Northwest Bay Shore Drive, Peshawbestown, Michigan, US, 49682
Last Update: 2025-11-28

Leelanau Sands Casino & Lodge is located at 2521 N West Bay Shore Dr, Peshawbestown, MI 49682 located on a scenic 20 miles north of Traverse City on M-22 in Peshawbestown, Michigan. Our casino floor offers blackjack, roulette, poker, and bingo - ensuring there is a casino table game for everyone to enjoy! Visit our website for current hours of operation at: https://www.leelanausandscasino.com/hours-of-operation

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/gaming-capital-group.jpeg
Gaming Capital Group, LLC
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/leelanau-sands-casino-and-lodge.jpeg
Leelanau Sands Casino & Lodge
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
Gaming Capital Group, LLC
100%
Compliance Rate
0/4 Standards Verified
Leelanau Sands Casino & Lodge
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 Gaming Capital Group, LLC in 2025.

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

No incidents recorded for Leelanau Sands Casino & Lodge in 2025.

Incident History — Gaming Capital Group, LLC (X = Date, Y = Severity)

Gaming Capital Group, LLC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Leelanau Sands Casino & Lodge (X = Date, Y = Severity)

Leelanau Sands Casino & Lodge cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gaming-capital-group.jpeg
Gaming Capital Group, LLC
Incidents

No Incident

https://images.rankiteo.com/companyimages/leelanau-sands-casino-and-lodge.jpeg
Leelanau Sands Casino & Lodge
Incidents

No Incident

FAQ

Gaming Capital Group, LLC company demonstrates a stronger AI Cybersecurity Score compared to Leelanau Sands Casino & Lodge company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Leelanau Sands Casino & Lodge company has disclosed a higher number of cyber incidents compared to Gaming Capital Group, LLC company.

In the current year, Leelanau Sands Casino & Lodge company and Gaming Capital Group, LLC company have not reported any cyber incidents.

Neither Leelanau Sands Casino & Lodge company nor Gaming Capital Group, LLC company has reported experiencing a ransomware attack publicly.

Neither Leelanau Sands Casino & Lodge company nor Gaming Capital Group, LLC company has reported experiencing a data breach publicly.

Neither Leelanau Sands Casino & Lodge company nor Gaming Capital Group, LLC company has reported experiencing targeted cyberattacks publicly.

Neither Gaming Capital Group, LLC company nor Leelanau Sands Casino & Lodge company has reported experiencing or disclosing vulnerabilities publicly.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds any compliance certifications.

Neither company holds any compliance certifications.

Leelanau Sands Casino & Lodge company has more subsidiaries worldwide compared to Gaming Capital Group, LLC company.

Gaming Capital Group, LLC company employs more people globally than Leelanau Sands Casino & Lodge company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds SOC 2 Type 1 certification.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds SOC 2 Type 2 certification.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds ISO 27001 certification.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds PCI DSS certification.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge holds HIPAA certification.

Neither Gaming Capital Group, LLC nor Leelanau Sands Casino & Lodge 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