Comparison Overview

MrQ

VS

Quechan Casino Resort & Paradise Casino

MrQ

8 Sandridge Park, St Albans, undefined, AL3 6PH, GB
Last Update: 2025-11-27
Between 750 and 799

At MrQ, we're all about no-nonsense fun, served with a side of quirk. We don’t believe in overpromises or jargon—just straightforward gaming that brings joy to our players’ everyday life, with a personal touch that’s as delightful as it is refreshing. We’re not just shaking up the casino industry—we’re redefining the way we work too. We encourage creativity, risk-taking, and getting shit done with passion and fun. Our team is united by a shared desire for delivering an honest, unique experience to our players, and we believe that starts with how we treat each other. Here, your ideas are valued, your growth is supported, and your work truly makes an impact. Check out our open vacancies at careers.lindar.com and see where you can make your mark at MrQ!

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

Quechan Casino Resort & Paradise Casino

None
Last Update: 2025-11-27
Between 750 and 799

Do what you love when you want to do it at Quechan Casino • Resort! Escape into the extraordinary – an immersion in sights, sounds and experiences that remain with you. Play with passion in our sprawling casino featuring more than 1,000 slot machines plus table games, a large live poker room and the region’s only high-limit room. Dine as you desire at any of our four distinctive restaurants. Enjoy exciting nightlife at our popular bars. See live performances by both local artists and national headliners! Relax in any of our luxurious, amenity-rich hotel rooms including 8 spacious suites. A room at Quechan Casino Resort is also a great home base for exploring Yuma’s historic and tribal attractions. The possibilities are endless while you’re here. We hope to see you soon!

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 175
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/lindar-media.jpeg
MrQ
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/quechan-casino-resort.jpeg
Quechan Casino Resort & Paradise 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
MrQ
100%
Compliance Rate
0/4 Standards Verified
Quechan Casino Resort & Paradise 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 MrQ in 2025.

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

No incidents recorded for Quechan Casino Resort & Paradise Casino in 2025.

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

MrQ cyber incidents detection timeline including parent company and subsidiaries

Incident History — Quechan Casino Resort & Paradise Casino (X = Date, Y = Severity)

Quechan Casino Resort & Paradise Casino cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/lindar-media.jpeg
MrQ
Incidents

No Incident

https://images.rankiteo.com/companyimages/quechan-casino-resort.jpeg
Quechan Casino Resort & Paradise Casino
Incidents

No Incident

FAQ

Quechan Casino Resort & Paradise Casino company demonstrates a stronger AI Cybersecurity Score compared to MrQ company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Quechan Casino Resort & Paradise Casino company has disclosed a higher number of cyber incidents compared to MrQ company.

In the current year, Quechan Casino Resort & Paradise Casino company and MrQ company have not reported any cyber incidents.

Neither Quechan Casino Resort & Paradise Casino company nor MrQ company has reported experiencing a ransomware attack publicly.

Neither Quechan Casino Resort & Paradise Casino company nor MrQ company has reported experiencing a data breach publicly.

Neither Quechan Casino Resort & Paradise Casino company nor MrQ company has reported experiencing targeted cyberattacks publicly.

Neither MrQ company nor Quechan Casino Resort & Paradise Casino company has reported experiencing or disclosing vulnerabilities publicly.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds any compliance certifications.

Neither company holds any compliance certifications.

Neither MrQ company nor Quechan Casino Resort & Paradise Casino company has publicly disclosed detailed information about the number of their subsidiaries.

Quechan Casino Resort & Paradise Casino company employs more people globally than MrQ company, reflecting its scale as a Gambling Facilities and Casinos.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds SOC 2 Type 1 certification.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds SOC 2 Type 2 certification.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds ISO 27001 certification.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds PCI DSS certification.

Neither MrQ nor Quechan Casino Resort & Paradise Casino holds HIPAA certification.

Neither MrQ nor Quechan Casino Resort & Paradise 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