Comparison Overview

del Lago Resort & Casino

VS

Amaya

del Lago Resort & Casino

1133 Route 414, Waterloo, NY, 13165, US
Last Update: 2025-11-27
Between 750 and 799

The FLX Region’s #1 casino! The hottest slots, thrilling table games, electrifying entertainment, state-of-art Sportsbook and luxurious hotel and spa! We’re del Lago. In Italy, it means “of the lakes.” But around here, it means so much more. It’s a way of life, a ready-for-anything attitude that’s a spicy mix of old world charm and homegrown hospitality.   It’s adventure and excitement, best friends and unforgettable times, big-name entertainment and small-town values.   And it’s a commitment to excellence that drives everything we do.   Choose from our customizable event spaces to celebrate your wedding, business meeting or special event planning.   del Lago Resort & Casino is the Finger Lakes #1 Resort and Casino.

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

Amaya

7600 Trans Canada Hwy, Pointe-Claire, Quebec, H9R1C8, CA
Last Update: 2025-11-28
Between 750 and 799

Amaya is a leading provider of technology-based solutions, products and services in the global gaming and interactive entertainment industries. Amaya owns gaming and related consumer businesses and brands including PokerStars, Full Tilt, StarsDraft, the European Poker Tour, PokerStars Caribbean Adventure, the Latin American Poker Tour and the Asia Pacific Poker Tour. These brands collectively form the largest poker business in the world, comprising online poker games and tournaments, live poker competitions, branded poker rooms in popular casinos in major cities around the world, and poker programming created for television and online audiences. Amaya, through certain of these brands, also offers non-poker online gaming products, including casino, sportsbook and daily fantasy sports.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/del-lago-resort-&-casino.jpeg
del Lago Resort & 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
https://images.rankiteo.com/companyimages/amaya.jpeg
Amaya
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
del Lago Resort & Casino
100%
Compliance Rate
0/4 Standards Verified
Amaya
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 del Lago Resort & Casino in 2025.

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

No incidents recorded for Amaya in 2025.

Incident History — del Lago Resort & Casino (X = Date, Y = Severity)

del Lago Resort & Casino cyber incidents detection timeline including parent company and subsidiaries

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

Amaya cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/del-lago-resort-&-casino.jpeg
del Lago Resort & Casino
Incidents

No Incident

https://images.rankiteo.com/companyimages/amaya.jpeg
Amaya
Incidents

No Incident

FAQ

del Lago Resort & Casino company demonstrates a stronger AI Cybersecurity Score compared to Amaya company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Amaya company has disclosed a higher number of cyber incidents compared to del Lago Resort & Casino company.

In the current year, Amaya company and del Lago Resort & Casino company have not reported any cyber incidents.

Neither Amaya company nor del Lago Resort & Casino company has reported experiencing a ransomware attack publicly.

Neither Amaya company nor del Lago Resort & Casino company has reported experiencing a data breach publicly.

Neither Amaya company nor del Lago Resort & Casino company has reported experiencing targeted cyberattacks publicly.

Neither del Lago Resort & Casino company nor Amaya company has reported experiencing or disclosing vulnerabilities publicly.

Neither del Lago Resort & Casino nor Amaya holds any compliance certifications.

Neither company holds any compliance certifications.

del Lago Resort & Casino company has more subsidiaries worldwide compared to Amaya company.

del Lago Resort & Casino company employs more people globally than Amaya company, reflecting its scale as a Gambling Facilities and Casinos.

Neither del Lago Resort & Casino nor Amaya holds SOC 2 Type 1 certification.

Neither del Lago Resort & Casino nor Amaya holds SOC 2 Type 2 certification.

Neither del Lago Resort & Casino nor Amaya holds ISO 27001 certification.

Neither del Lago Resort & Casino nor Amaya holds PCI DSS certification.

Neither del Lago Resort & Casino nor Amaya holds HIPAA certification.

Neither del Lago Resort & Casino nor Amaya holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

Risk Information
cvss4
Base: 6.2
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

Risk Information
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Description

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.