Comparison Overview

bet365

VS

Reel Time Gaming

bet365

bet365 House, Stoke-on-Trent, Staffordshire, ST1 5SZ, GB
Last Update: 2025-11-27

At bet365, we’re a global leader in online gambling, revolutionising the industry since 2000. Founded by Denise Coates CBE, we now employ over 9,000 people and serve over 100 million customers in 21 languages. Our focus on In-Play betting has solidified our market-leading position, offering an unmatched experience across 96 sports and over 1 million live streams. With over 750 concurrent sporting fixtures at peak and more live sports streamed than anyone else in Europe, we handle over 6 billion HTTP requests daily and process more than 2 million bets per hour at peak. Innovation thrives and creativity is celebrated at bet365. We empower our employees to push boundaries and explore new ideas, cultivating a culture that encourages and rewards creativity. With endless opportunities for growth and collaboration, team members have the chance to make a real impact in the world of online gambling. As a forward-thinking company, we’re breaking new ground in software innovation—together, we’re redefining what’s possible!

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

Reel Time Gaming

Suite 1A,, Taringa, QLD, 4068, AU
Last Update: 2025-11-27

Reel Time Gaming provides world class games to the gambling industry throughout the world. We have a multi-disciplinary team of software developers, game designers, mathematicians, artists and testers including members with over 30 years experience in the industry. Reel Time Gaming provides support for the full life-cycle of the game from the initial concept through to approval. With games that have stunning graphics, powerful themes and state of the art mathematical models, we have created over 100 titles for several manufacturers and operators which are currently running in an increasing number of jurisdictions around the world.

NAICS: 713
NAICS Definition:
Employees: 53
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/bet365.jpeg
bet365
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/reel-time-gaming.jpeg
Reel Time 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
bet365
100%
Compliance Rate
0/4 Standards Verified
Reel Time 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 bet365 in 2025.

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

No incidents recorded for Reel Time Gaming in 2025.

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

bet365 cyber incidents detection timeline including parent company and subsidiaries

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

Reel Time Gaming cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bet365.jpeg
bet365
Incidents

No Incident

https://images.rankiteo.com/companyimages/reel-time-gaming.jpeg
Reel Time Gaming
Incidents

No Incident

FAQ

bet365 company demonstrates a stronger AI Cybersecurity Score compared to Reel Time Gaming company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Reel Time Gaming company has disclosed a higher number of cyber incidents compared to bet365 company.

In the current year, Reel Time Gaming company and bet365 company have not reported any cyber incidents.

Neither Reel Time Gaming company nor bet365 company has reported experiencing a ransomware attack publicly.

Neither Reel Time Gaming company nor bet365 company has reported experiencing a data breach publicly.

Neither Reel Time Gaming company nor bet365 company has reported experiencing targeted cyberattacks publicly.

Neither bet365 company nor Reel Time Gaming company has reported experiencing or disclosing vulnerabilities publicly.

Neither bet365 nor Reel Time Gaming holds any compliance certifications.

Neither company holds any compliance certifications.

bet365 company has more subsidiaries worldwide compared to Reel Time Gaming company.

bet365 company employs more people globally than Reel Time Gaming company, reflecting its scale as a Gambling Facilities and Casinos.

Neither bet365 nor Reel Time Gaming holds SOC 2 Type 1 certification.

Neither bet365 nor Reel Time Gaming holds SOC 2 Type 2 certification.

Neither bet365 nor Reel Time Gaming holds ISO 27001 certification.

Neither bet365 nor Reel Time Gaming holds PCI DSS certification.

Neither bet365 nor Reel Time Gaming holds HIPAA certification.

Neither bet365 nor Reel Time 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