Comparison Overview

PlayUp

VS

Pavilion Payments

PlayUp

48 Epsom Rd, Sydney, undefined, undefined, AU
Last Update: 2025-11-27

PlayUp is a next generation entertainment and technology group that enriches the lives of people through entertaining, rewarding and responsible online betting. We develop innovative betting technologies in-house to power our brands and deliver world-class user experiences. Our energies are focused on fulfilling the needs of dedicated and passionate users who seek a deeper connection to the games they play. PlayUp unifies the world's favourite online betting products including Fixed Odds Sports Betting, Fixed-Odds Racing (Horses and Greyhounds), Esports and Daily Fantasy Sports (DFS) where we host Australia’s largest and indeed some of the globe’s largest prize pools in competitive peer-to-peer online betting. We hold online betting licenses in multiple jurisdictions and currently operate in Australia, New Zealand, India and have recently launched in the USA.

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

Pavilion Payments

7201 W Lake Mead Blvd , 501, Las Vegas, NV, US, 89128
Last Update: 2025-11-27
Between 750 and 799

Pavilion Payments enables the world’s gaming entertainment leaders to create amazing consumer experiences and maximize spend across all of their physical and digital properties. Our complete suite of payment solutions enables safe, secure and trusted cash access at the cage, on the casino floor, or online. Our compliance and security solutions offer additional layers of automation and risk protection. And our analytics solutions enable clients to view performance across all of their gaming properties. Visit our website at pavilionpayments.com to learn more about our solutions for casino debit and credit card cash advance, e-check, ATM, full-service TITO and payment kiosks, Anti-Money Laundering (AML) compliance assistance, layered security, and analytics.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 149
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/playup-ltd.jpeg
PlayUp
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/pavilion-payments.jpeg
Pavilion Payments
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
PlayUp
100%
Compliance Rate
0/4 Standards Verified
Pavilion Payments
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 PlayUp in 2025.

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

No incidents recorded for Pavilion Payments in 2025.

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

PlayUp cyber incidents detection timeline including parent company and subsidiaries

Incident History — Pavilion Payments (X = Date, Y = Severity)

Pavilion Payments cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/playup-ltd.jpeg
PlayUp
Incidents

No Incident

https://images.rankiteo.com/companyimages/pavilion-payments.jpeg
Pavilion Payments
Incidents

No Incident

FAQ

Pavilion Payments company demonstrates a stronger AI Cybersecurity Score compared to PlayUp company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Pavilion Payments company has disclosed a higher number of cyber incidents compared to PlayUp company.

In the current year, Pavilion Payments company and PlayUp company have not reported any cyber incidents.

Neither Pavilion Payments company nor PlayUp company has reported experiencing a ransomware attack publicly.

Neither Pavilion Payments company nor PlayUp company has reported experiencing a data breach publicly.

Neither Pavilion Payments company nor PlayUp company has reported experiencing targeted cyberattacks publicly.

Neither PlayUp company nor Pavilion Payments company has reported experiencing or disclosing vulnerabilities publicly.

Neither PlayUp nor Pavilion Payments holds any compliance certifications.

Neither company holds any compliance certifications.

Neither PlayUp company nor Pavilion Payments company has publicly disclosed detailed information about the number of their subsidiaries.

Pavilion Payments company employs more people globally than PlayUp company, reflecting its scale as a Gambling Facilities and Casinos.

Neither PlayUp nor Pavilion Payments holds SOC 2 Type 1 certification.

Neither PlayUp nor Pavilion Payments holds SOC 2 Type 2 certification.

Neither PlayUp nor Pavilion Payments holds ISO 27001 certification.

Neither PlayUp nor Pavilion Payments holds PCI DSS certification.

Neither PlayUp nor Pavilion Payments holds HIPAA certification.

Neither PlayUp nor Pavilion Payments 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