Comparison Overview

L'Auberge Baton Rouge

VS

Hollywood Casino at Greektown

L'Auberge Baton Rouge

777 L’Auberge Avenue, Baton Rouge, LA, 70820, US
Last Update: 2025-11-27
Between 750 and 799

L’Auberge Casino & Hotel Baton Rouge is a $368-million premier southern facility located on 575 acres of land in Baton Rouge, La., off Nicholson Drive in East Baton Rouge Parish. L’Auberge captures the feel of a Southern river lodge and embraces Louisiana's rich cultural history, food, music and ‘laissez les bon temps rouler’ way of life. L’Auberge includes an expansive single-level, 74,000 square foot casino; nearly 1,500 slot machines; 50 table games, including a poker room; a 12-story hotel with 205 guest rooms, unique rooftop pool and state-of the-art fitness center overlooking the Mississippi River; four dining outlets; a unique casino nightclub with breathtaking views of the river; and 2,400 total parking spaces, including 800 in a covered parking garage.

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

Hollywood Casino at Greektown

555 East Lafayette Ave, Detroit, Michigan, 48226, US
Last Update: 2025-11-27

Hollywood Casino at Greektown Located in the heart of downtown Detroit in the historic Greektown district, Hollywood Casino at Greektown offers over 100,000 square feet of gaming, entertainment and dining experiences. With 400 stunning guestrooms and suites devoted to your comfort, our 30-story hotel is the perfect place to relax and recharge after a night on the town, to get ready for a trip to our casino, or just to see what sights and destinations the dynamic and exciting Greektown district has in store. For more information, please visit, www.HollywoodGreektown.com.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 716
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/l'auberge-baton-rouge.jpeg
L'Auberge Baton Rouge
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/greektown-casino.jpeg
Hollywood Casino at Greektown
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
L'Auberge Baton Rouge
100%
Compliance Rate
0/4 Standards Verified
Hollywood Casino at Greektown
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 L'Auberge Baton Rouge in 2025.

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

No incidents recorded for Hollywood Casino at Greektown in 2025.

Incident History — L'Auberge Baton Rouge (X = Date, Y = Severity)

L'Auberge Baton Rouge cyber incidents detection timeline including parent company and subsidiaries

Incident History — Hollywood Casino at Greektown (X = Date, Y = Severity)

Hollywood Casino at Greektown cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/l'auberge-baton-rouge.jpeg
L'Auberge Baton Rouge
Incidents

No Incident

https://images.rankiteo.com/companyimages/greektown-casino.jpeg
Hollywood Casino at Greektown
Incidents

No Incident

FAQ

Hollywood Casino at Greektown company demonstrates a stronger AI Cybersecurity Score compared to L'Auberge Baton Rouge company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Hollywood Casino at Greektown company has disclosed a higher number of cyber incidents compared to L'Auberge Baton Rouge company.

In the current year, Hollywood Casino at Greektown company and L'Auberge Baton Rouge company have not reported any cyber incidents.

Neither Hollywood Casino at Greektown company nor L'Auberge Baton Rouge company has reported experiencing a ransomware attack publicly.

Neither Hollywood Casino at Greektown company nor L'Auberge Baton Rouge company has reported experiencing a data breach publicly.

Neither Hollywood Casino at Greektown company nor L'Auberge Baton Rouge company has reported experiencing targeted cyberattacks publicly.

Neither L'Auberge Baton Rouge company nor Hollywood Casino at Greektown company has reported experiencing or disclosing vulnerabilities publicly.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds any compliance certifications.

Neither company holds any compliance certifications.

L'Auberge Baton Rouge company has more subsidiaries worldwide compared to Hollywood Casino at Greektown company.

Hollywood Casino at Greektown company employs more people globally than L'Auberge Baton Rouge company, reflecting its scale as a Gambling Facilities and Casinos.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds SOC 2 Type 1 certification.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds SOC 2 Type 2 certification.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds ISO 27001 certification.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds PCI DSS certification.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown holds HIPAA certification.

Neither L'Auberge Baton Rouge nor Hollywood Casino at Greektown 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