Comparison Overview

Coral

VS

California Hotel & Casino

Coral

Stratford Place Westfield Stratford City , London, Newham, E20 1EJ, GB
Last Update: 2025-11-26

Coral is a leading European betting and gaming company with strong market positions, high growth and well-established brands, both on the high street and online. We serve customers primarily in the UK and Italy; the two largest regulated gambling markets in Europe. The Group is proud to be the first gambling company to have received full GamCare accreditation across all its UK divisions. Online - The Group provides market-leading sports betting and gaming products for mobile, desktop and tablet devices through its brands: Coral.co.uk, Galabingo.com, Galacasino.com and Eurobet.it.

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

California Hotel & Casino

12 East Ogden Avenue, Las Vegas, Nevada, 89101, US
Last Update: 2025-11-21
Between 750 and 799

The hospitality of the Hawaiian Islands will flower during your visit to the California Hotel Casino. We like to say "Aloha"​ is spoken fluently here, and our guests enjoy many Hawaiian touches, ranging from dining delicacies such as oxtail soup to the colorful decor reminiscent of the islands'​ lush, tropical beauty.

NAICS: 713
NAICS Definition:
Employees: 77
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/gala-coral-group.jpeg
Coral
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/thecal.jpeg
California Hotel & 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
Compliance Summary
Coral
100%
Compliance Rate
0/4 Standards Verified
California Hotel & Casino
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 Coral in 2025.

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

No incidents recorded for California Hotel & Casino in 2025.

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

Coral cyber incidents detection timeline including parent company and subsidiaries

Incident History — California Hotel & Casino (X = Date, Y = Severity)

California Hotel & Casino cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/gala-coral-group.jpeg
Coral
Incidents

Date Detected: 12/2017
Type:Data Leak
Attack Vector: Hacking
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/thecal.jpeg
California Hotel & Casino
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

Coral company demonstrates a stronger AI Cybersecurity Score compared to California Hotel & Casino company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

California Hotel & Casino company has faced a higher number of disclosed cyber incidents historically compared to Coral company.

In the current year, California Hotel & Casino company has reported more cyber incidents than Coral company.

Neither California Hotel & Casino company nor Coral company has reported experiencing a ransomware attack publicly.

California Hotel & Casino company has disclosed at least one data breach, while Coral company has not reported such incidents publicly.

Neither California Hotel & Casino company nor Coral company has reported experiencing targeted cyberattacks publicly.

Neither Coral company nor California Hotel & Casino company has reported experiencing or disclosing vulnerabilities publicly.

Neither Coral nor California Hotel & Casino holds any compliance certifications.

Neither company holds any compliance certifications.

California Hotel & Casino company has more subsidiaries worldwide compared to Coral company.

Coral company employs more people globally than California Hotel & Casino company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Coral nor California Hotel & Casino holds SOC 2 Type 1 certification.

Neither Coral nor California Hotel & Casino holds SOC 2 Type 2 certification.

Neither Coral nor California Hotel & Casino holds ISO 27001 certification.

Neither Coral nor California Hotel & Casino holds PCI DSS certification.

Neither Coral nor California Hotel & Casino holds HIPAA certification.

Neither Coral nor California Hotel & Casino 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