Protect casino and hotel servers from ransomware.

As amended effective 29 January 2026, it asks you to notify the Chair within 24 hours of activating your incident response procedures. An initial report follows within 5 calendar days and written updates every 30 days. The investigation report covers root cause, extent and the actions taken to prevent a repeat. Mimic files none of it.

Mimic protects the servers behind the floor and the hotel. On the floor, that's casino management, player tracking and slot accounting servers. In the hotel, it's property management and point-of-sale back-office servers. Loyalty databases and Active Directory sit behind both. Each gets a Mimic node and its own known-good profile. Gaming machines, kiosks, workstations, laptops and network devices stay out of scope.

Start with the domain controllers, because the systems on the floor and in the hotel trust them. The floor, the hotel and the back office all sign in through the same domain controllers. With protections turned on, a Mimic node on each one locks Group Policy permissions and blocks stops of critical services. Nothing installs on guest-facing terminals, workstations or laptops.

On a protected server, when the change falls outside its known-good profile, yes. Mimic checks what a session changes, not who logged in, so an attacker who talks the help desk into an admin password reset still meets the same check. The unauthorized change stops at the point of execution, and DashCam records what was attempted, by which process and when.