Comparison Overview

Castle Hill Gaming

VS

Native Gaming

Castle Hill Gaming

2065 Inglewood Drive, Charlottesville, Virginia, 22901, US
Last Update: 2025-11-28

Castle Hill Gaming is a prominent provider of Class II, Class III, and HHR gaming machines to Indian and Commercial Casinos across the United States, with offices located in Charlottesville, VA, Tulsa, OK, and Manchester, NH. CHG offers exciting employment opportunities for individuals passionate about the gaming industry. As an industry leader, CHG emphasizes innovation, customer satisfaction, and adherence to regulatory standards. This is an exceptional chance to become part of a thriving organization with a strong market presence. Apply now to contribute to the growth of cutting-edge gaming solutions and deliver exceptional customer experiences. Join Castle Hill Gaming and be a part of the exciting world of casino gaming.

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

Native Gaming

undefined, Los Angeles, California, undefined, US
Last Update: 2025-11-27
Between 750 and 799

Native Gaming (NativeGaming.io) is an ambitious new online casino that allows players to "Be the House" by directly taking a stake in the bankroll. Stakeholders receive Gross Gaming Revenue generated by 5,000+ Casino Games from over 70 game providers, including Evolution Gaming, Netent, Play'n GO and Microgaming. Native Gaming recently announced its proprietary Social MMO Sweepstakes Casino featuring the first-of-its-kind, patent-pending Native MMO Slot Game.

NAICS: 713
NAICS Definition:
Employees: 8
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/castle-hill-gaming.jpeg
Castle Hill 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
https://images.rankiteo.com/companyimages/nativegaming.jpeg
Native 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
Castle Hill Gaming
100%
Compliance Rate
0/4 Standards Verified
Native 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 Castle Hill Gaming in 2025.

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

No incidents recorded for Native Gaming in 2025.

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

Castle Hill Gaming cyber incidents detection timeline including parent company and subsidiaries

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

Native Gaming cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/castle-hill-gaming.jpeg
Castle Hill Gaming
Incidents

No Incident

https://images.rankiteo.com/companyimages/nativegaming.jpeg
Native Gaming
Incidents

No Incident

FAQ

Both Castle Hill Gaming company and Native Gaming company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Native Gaming company has disclosed a higher number of cyber incidents compared to Castle Hill Gaming company.

In the current year, Native Gaming company and Castle Hill Gaming company have not reported any cyber incidents.

Neither Native Gaming company nor Castle Hill Gaming company has reported experiencing a ransomware attack publicly.

Neither Native Gaming company nor Castle Hill Gaming company has reported experiencing a data breach publicly.

Neither Native Gaming company nor Castle Hill Gaming company has reported experiencing targeted cyberattacks publicly.

Neither Castle Hill Gaming company nor Native Gaming company has reported experiencing or disclosing vulnerabilities publicly.

Neither Castle Hill Gaming nor Native Gaming holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Castle Hill Gaming company nor Native Gaming company has publicly disclosed detailed information about the number of their subsidiaries.

Castle Hill Gaming company employs more people globally than Native Gaming company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Castle Hill Gaming nor Native Gaming holds SOC 2 Type 1 certification.

Neither Castle Hill Gaming nor Native Gaming holds SOC 2 Type 2 certification.

Neither Castle Hill Gaming nor Native Gaming holds ISO 27001 certification.

Neither Castle Hill Gaming nor Native Gaming holds PCI DSS certification.

Neither Castle Hill Gaming nor Native Gaming holds HIPAA certification.

Neither Castle Hill Gaming nor Native 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