Comparison Overview

San Manuel Casino

VS

Games Inc

San Manuel Casino

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

Since 1986, Yaamava' Resort & Casino at San Manuel, formerly known as San Manuel Casino, has built a strong reputation as a premier and renowned casino and Southern California’s one-stop destination for entertainment and fun. Millions of guests each year enjoy Las Vegas-style gaming, sumptuous dining, and more than 6,500 of the newest slot machines. With exceptional guest experiences and a multitude of highly rewarding professional careers, it is an anchor for the local economy and among the largest private employers in San Bernardino County. We are proud to be a Great Place to Work-Certified™ company! Become a part of our team today!

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

Games Inc

Pinewood Business Park, Coleshill Road, Solihull, B37 7HG, GB
Last Update: 2025-11-27
Between 750 and 799

Games Inc is a trusted casino content studio with over 10 years of experience creating premium games for operators around the world. We develop high-quality slots, innovative table games, and fast-paced crash titles — all designed to engage, retain, and deliver results. Our studio was built on a commitment to craft and collaboration. We’ve spent years working closely with leading operators to deliver bespoke, technically sound games that meet commercial goals and regulatory demands. Backed by our own RGS platform and licences, we control every step of the process — from concept to launch. Now entering a new phase of growth, we’re scaling our distribution, increasing output, and expanding into new markets. Whether you’re an operator, aggregator, or partner — Games Inc is ready to deliver the content that makes your portfolio shine.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 124
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/san-manuel-casino.jpeg
San Manuel Casino
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/games-inc.jpeg
Games Inc
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
San Manuel Casino
100%
Compliance Rate
0/4 Standards Verified
Games Inc
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 San Manuel Casino in 2025.

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

No incidents recorded for Games Inc in 2025.

Incident History — San Manuel Casino (X = Date, Y = Severity)

San Manuel Casino cyber incidents detection timeline including parent company and subsidiaries

Incident History — Games Inc (X = Date, Y = Severity)

Games Inc cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/san-manuel-casino.jpeg
San Manuel Casino
Incidents

No Incident

https://images.rankiteo.com/companyimages/games-inc.jpeg
Games Inc
Incidents

No Incident

FAQ

San Manuel Casino company demonstrates a stronger AI Cybersecurity Score compared to Games Inc company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Games Inc company has disclosed a higher number of cyber incidents compared to San Manuel Casino company.

In the current year, Games Inc company and San Manuel Casino company have not reported any cyber incidents.

Neither Games Inc company nor San Manuel Casino company has reported experiencing a ransomware attack publicly.

Neither Games Inc company nor San Manuel Casino company has reported experiencing a data breach publicly.

Neither Games Inc company nor San Manuel Casino company has reported experiencing targeted cyberattacks publicly.

Neither San Manuel Casino company nor Games Inc company has reported experiencing or disclosing vulnerabilities publicly.

Neither San Manuel Casino nor Games Inc holds any compliance certifications.

Neither company holds any compliance certifications.

Neither San Manuel Casino company nor Games Inc company has publicly disclosed detailed information about the number of their subsidiaries.

San Manuel Casino company employs more people globally than Games Inc company, reflecting its scale as a Gambling Facilities and Casinos.

Neither San Manuel Casino nor Games Inc holds SOC 2 Type 1 certification.

Neither San Manuel Casino nor Games Inc holds SOC 2 Type 2 certification.

Neither San Manuel Casino nor Games Inc holds ISO 27001 certification.

Neither San Manuel Casino nor Games Inc holds PCI DSS certification.

Neither San Manuel Casino nor Games Inc holds HIPAA certification.

Neither San Manuel Casino nor Games Inc 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