CS2 server protection
Protection that sits on your dedicated server or Pterodactyl instance and reports into one operations panel.
Most CS2 “server protection” products are either a Discord bot that reads a denylist or a plugin that kicks too early. ImpactGuard is the plugin-plus-panel version: the game node enforces, the panel is the command center, and you keep role-separated admin access.
Dedicated and Pterodactyl
On a raw dedicated box you extract the zip once and manage Panel.json yourself. On Pterodactyl you do the same inside the server filesystem — the egg does not replace Metamod or CounterStrikeSharp. The panel stays on impactguard.ac; game nodes only need outbound HTTPS for license and heartbeat.
Operational loop
- Heartbeat about every 60 seconds so the server shows online.
- Config / global override sync about every 120 seconds.
- Detections stream to the panel for the staff who should see them.
- Players use appeals instead of arguing in chat.
Network-sized thinking
One license covers CS2 and CS 1.6 up to your plan’s slot count. If you host both games, do not invent a second vendor just because GoldSrc is old. See CS 1.6 anti-cheat and plans.
Status for the control plane is status.impactguard.ac. The game server can be healthy while the panel is in maintenance — treat them as two systems.
Questions operators ask
Does ImpactGuard work on Pterodactyl?
Yes. Install Metamod and CounterStrikeSharp in the CS2 server image, extract the ImpactGuard zip at the server root, and set the license. The panel does not need to run on the game node.
Windows or Linux?
Both. The CS2 package targets dedicated servers on Windows and Linux with CounterStrikeSharp 1.0.368+.