Comparison Overview

Dragonfish

VS

Hard Rock Casino Cincinnati

Dragonfish

601-701 Europort, Gibraltar, undefined, Europort, GI
Last Update: 2025-11-27

As the independent B2B division of 888, Dragonfish has proven credentials and a renowned, trustworthy management team with extensive experience in all aspects of the regulated gaming market. Our partners enjoy a strategic partnership complete with comprehensive end-to-end service; global reach, resources and contacts; and specific experience across local markets. Established in 2007, we’ve already helped many global partners achieve their goals in online gaming. The Dragonfish online gaming platform is licensed and certified in multiple regulated jurisdictions, including a license from the UK Gambling Commission and certification from eCogra. Whether you’re looking to take your gaming environment online or to enhance your existing operations, Dragonfish can power your regulated market offering with our rich game experience and outstanding content portfolio. While your business benefits from our flexibility and dedicated customer service, Dragonfish will give your B2C offering a valuable competitive edge. Online success demands an integrated partnership approach. Dragonfish offers you uniquely powerful, flexible and customizable solutions, across games, technology, marketing and operations, to help maximise lifetime customer value to your business. As devoted professionals in the gaming industry, we as a company, invest heavily in responsible gaming practices, an integral part of our corporate culture.

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

Hard Rock Casino Cincinnati

1000 Broadway Street, Cincinnati, 45202, US
Last Update: 2025-11-27

The Queen City of the Midwest, Cincinnati, Ohio, is now home to Hard Rock Casino Cincinnati. Hard Rock Casino Cincinnati opened on 10/29/2021. Set on 22 acres of land in Pendleton's trendy neighborhood, it is five minutes north of the Ohio River, two major league sports stadiums, and ample shopping in OTR. With restaurants to satisfy everyone's taste pallets in your group, including a Hard Rock Cafe. The Hard Rock Casino Cincinnati is owned and operated by Hard Rock. Employees at the Hard Rock Casino Cincinnati are employed by Hard Rock. We are committed to fostering diversity, equity, and inclusion. DE&I aims to address the needs of all team members - including Native Americans, women, LGBTQ+ community, people of color (BIPOC), people with disabilities and military veterans. Diversity: is the celebration of differences and leveraging those differences to produce stellar results. Equity: is a process of seeking fairness through deliberate and intentional actions. Inclusion: is when everyone has the freedom and comfort to express their thoughts ides, and options in a safe, trusting, and open environment. Must be 21 or older to gamble. Gambling Problem? Call 1-800-589-9966.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 292
Subsidiaries: 33
12-month incidents
0
Known data breaches
3
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/dragonfish.jpeg
Dragonfish
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/hardrockcincinnati.jpeg
Hard Rock Casino Cincinnati
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
Dragonfish
100%
Compliance Rate
0/4 Standards Verified
Hard Rock Casino Cincinnati
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 Dragonfish in 2025.

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

No incidents recorded for Hard Rock Casino Cincinnati in 2025.

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

Dragonfish cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hard Rock Casino Cincinnati (X = Date, Y = Severity)

Hard Rock Casino Cincinnati cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dragonfish.jpeg
Dragonfish
Incidents

No Incident

https://images.rankiteo.com/companyimages/hardrockcincinnati.jpeg
Hard Rock Casino Cincinnati
Incidents

Date Detected: 07/2017
Type:Breach
Attack Vector: Compromised Internal Account
Motivation: Financial Gain
Blog: Blog

Date Detected: 5/2017
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 10/2015
Type:Cyber Attack
Attack Vector: Card Scraping Malware
Blog: Blog

FAQ

Hard Rock Casino Cincinnati company demonstrates a stronger AI Cybersecurity Score compared to Dragonfish company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Hard Rock Casino Cincinnati company has historically faced a number of disclosed cyber incidents, whereas Dragonfish company has not reported any.

In the current year, Hard Rock Casino Cincinnati company and Dragonfish company have not reported any cyber incidents.

Neither Hard Rock Casino Cincinnati company nor Dragonfish company has reported experiencing a ransomware attack publicly.

Hard Rock Casino Cincinnati company has disclosed at least one data breach, while Dragonfish company has not reported such incidents publicly.

Hard Rock Casino Cincinnati company has reported targeted cyberattacks, while Dragonfish company has not reported such incidents publicly.

Neither Dragonfish company nor Hard Rock Casino Cincinnati company has reported experiencing or disclosing vulnerabilities publicly.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds any compliance certifications.

Neither company holds any compliance certifications.

Hard Rock Casino Cincinnati company has more subsidiaries worldwide compared to Dragonfish company.

Hard Rock Casino Cincinnati company employs more people globally than Dragonfish company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds SOC 2 Type 1 certification.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds SOC 2 Type 2 certification.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds ISO 27001 certification.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds PCI DSS certification.

Neither Dragonfish nor Hard Rock Casino Cincinnati holds HIPAA certification.

Neither Dragonfish nor Hard Rock Casino Cincinnati 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