Protect game build and live-service servers from ransomware.

Put a Mimic node on each one and let it build a known-good profile of the repository or build service: the files, processes, services and settings it depends on. Once your team approves the profile and turns protections on, a change to anything in it outside an approved change stops at the point of execution. DashCam records what was attempted, by which process and when.

Enforcement overhead is tunable, and you measure it before you decide. Take a baseline of build times on your own pre-production agents, install Mimic, turn protections on and run the same builds again. Mimic decides inline, before the change executes. No reboots required, so the agents stay in the pool while you test.

Start where an outage stops a release: source control and artifact repository servers, then the build agents that pull from them. Live-service game and matchmaking servers come next, with the Active Directory the studio signs in through. Mimic Networks protects Windows Server 2016 and later, and Red Hat Enterprise Linux 8 and later, so check each server's operating system before you scope a proof of concept.

Developer workstations, consoles, player devices and network devices. Mimic Networks protects servers: Windows Server 2016 and later, and Red Hat Enterprise Linux 8 and later. Game servers on other Linux distributions aren't on that list, so check your fleet first. Mimic also doesn't scan code or sign builds. It controls what changes on the servers it protects, and nothing more.