Home / Purple Team Services / Gaming & Lottery — Tribal Gaming
Tribal Gaming Sector
A real-world purple team engagement inside a sovereign nation gaming operation | Fully anonymised | ISO 17025 accredited methodology
ISO 17025 Accredited · MITRE ATT&CK v15 · Conducted under explicit written authorisation
Sector
Tribal Gaming
Engagement
Purple Team Exercise
ATT&CK Tactics
MITRE ATT&CK v15
Location
United States
Purple Team Case Studies — Gaming & Lottery
ISO 17025 Accredited
MITRE ATT&CK v15
Conducted under explicit written authorisation
Confidentiality Notice: These case studies are anonymised; any resemblance to specific organisations is coincidental.
CASE STUDY GAM-CS-02
Ransomware Resilience and Tribal Gaming Regulatory Notification Testing — Tribal Casino-Resort
Validating business continuity and sovereign regulatory obligations under a simulated ransomware scenario
Organisation
A tribal casino-resort operating under a Tribal-State Compact with 2,100 gaming positions and an integrated resort (anonymised)
Sector
Gaming — Tribal gaming, sovereign nation operation
Location
United States — Tribal gaming jurisdiction
Engagement
Purple Team Exercise — Ransomware Resilience, OT/IT Boundary Testing, and Tribal Regulatory Notification Simulation
Duration
7 weeks (3-week scoping, 2-day exercise, 2-week remediation and reporting)
Frameworks
NIGC Minimum Internal Control Standards | Tribal-State Compact Cybersecurity Provisions | GLI-11 | NIST CSF 2.0 | MITRE ATT&CK Enterprise v15 | PCI DSS v4.0
Core Challenge
The tribal gaming commission had received updated cybersecurity guidance from the NIGC requiring tribal operations to demonstrate ransomware resilience under adversarial conditions. The engagement needed to validate three things: whether a ransomware attack originating in the hotel IT environment could reach the gaming floor systems; whether the tribe’s backup infrastructure was genuinely isolated from an attacker who had compromised the corporate network; and whether the tribal gaming commission notification process could meet the compact-specified 72-hour reporting window.
An additional requirement was testing the IT/OT boundary between the hotel property management system and the electronic gaming machine network.
Engagement Phases
Network Architecture Mapping and IT/OT Boundary Testing
Mapped the network segmentation between hotel PMS, corporate IT, and the EGM (electronic gaming machine) network. Found:Â a VLAN misconfiguration allowed lateral movement from the hotel network to the EGM management server. The EGM management server had administrative access to all 2,100 gaming machines. This pathway was undocumented and unknown to the IT team.
Backup Infrastructure Assessment
Tested whether ransomware precursor techniques could reach the backup infrastructure. Found:Â primary backups were replicated to a cloud storage account accessible using credentials stored in plaintext in a network share. Secondary tape backups were genuine air-gap but had not been tested for restoration in 14 months. Documented RTO: 48 hours. Tested RTO: 79 hours.
Lateral Movement Simulation: Hotel to Gaming Floor
Using the VLAN misconfiguration, simulated lateral movement from a compromised hotel workstation to the EGM management server. Found:Â no monitoring on east-west traffic between hotel and gaming VLANs. The EGM management server had no EDR deployed. From this position, a threat actor would have administrative control over the gaming floor without detection.
Ransomware Precursor Execution
Executed the standard ransomware precursor sequence: credential dumping, backup enumeration, shadow copy deletion, and data staging. Found:Â EDR detected credential dumping in 11 minutes (strong result). Shadow copy deletion was not detected. Backup enumeration was not detected. Cloud backup credentials were exfiltrated in this phase, invalidating the primary backup as a recovery option.
Business Continuity Plan Activation
Activated the documented BCP in parallel. Tested: time to switch to manual gaming floor operations; time to notify the tribal gaming commission; time to notify the Tribal-State Compact administrator; time to restore critical systems from the secondary tape backup. Findings:Â manual operations activated in 4 hours (within plan). Commission notification took 6 hours to initiate. Compact administrator was not notified within the 72-hour window.
Detection and Response Validation
Tested the full detection chain: SIEM, EDR, network monitoring, and the gaming floor surveillance integration. Found:Â the surveillance system had an API integration with the casino management system that was not monitored by the SIEM. This pathway remained active even during the simulated ransomware recovery exercise.
MITRE ATT&CK Techniques Tested
| ATT&CK ID | TECHNIQUE | DETECTION RESULT |
|---|---|---|
| T1199 | Trusted Relationship (Hotel-to-Gaming VLAN Misconfiguration) |
NOT DETECTED
No east-west monitoring between hotel and gaming VLANs. |
| T1021 | Remote Services (EGM Management Server Lateral Movement) |
NOT DETECTED
No EDR on EGM management server. No network monitoring. |
| T1490 | Inhibit System Recovery (Backup Enumeration) |
NOT DETECTED
Cloud backup credentials stored in plaintext. Not monitored. |
| T1003 | OS Credential Dumping |
DETECTED
EDR alert in 11 minutes. Strong result |
| T1489 | Service Stop (Shadow Copy Deletion) |
NOT DETECTED
No alert on VSS deletion on backup server. |
| T1567 | Exfiltration to Cloud Storage (Backup Credential Theft) |
NOT DETECTED
No DLP monitoring on cloud backup API calls. |
| T1078 | Valid Accounts (Casino Management System via Surveillance API) |
NOT DETECTED
Surveillance API not in SIEM scope. |
Outcomes
| METRIC | BEFORE | AFTER |
|---|---|---|
| IT/OT boundary (Hotel to EGM) | VLAN misconfiguration — hotel-to-gaming access possible | Misconfiguration remediated — segment confirmed isolated |
| Primary backup security | Cloud credentials in plaintext network share | Credential vault implemented — backup access requires MFA |
| Secondary backup RTO | Tested: 79 hours vs 48-hour documented RTO | Tape restoration retested: 51 hours. BCP updated. |
| EGM management server EDR | No EDR deployed | EDR deployed and tuned for gaming management traffic |
| NIGC regulatory notification | 72-hour window not achievable in simulation | Notification workflow documented and drilled — 6-hour initiation target |
| Compact administrator notification | Not completed within 72-hour window | Compact notification checklist created and assigned to GC |
| Surveillance API SIEM scope | Not monitored | Surveillance API integrated into SIEM scope |
“
The VLAN finding was the one that kept our CTO awake. We had spent two years hardening the perimeter and had never looked at whether someone already inside the hotel network could walk straight onto the gaming floor. The answer was yes. In a real incident, that is the difference between replacing a workstation and replacing the entire gaming management system.
Chief Compliance Officer, Regional P&C Carrier (anonymised)
Validate your tribal gaming security before your compact renewal examination
Strengthen your cybersecurity posture today.
Strengthen your cybersecurity posture and protect your organization from evolving threats. Discover how GLI Secure reduces risk, simplifies compliance, and protects customer trust.