| name | anti-cheat-systems |
| description | Analyze layered anti-cheat architecture, detection evidence, telemetry, and enforcement tradeoffs. Use for system-level defense questions; use narrower skills for DMA, kernel, graphics, mobile, or server details. |
Anti-cheat systems
Map the protected asset, attacker capability, observation point, detector, and enforcement authority. Separate confirmed product behavior from general defensive patterns.
Topic routing
- Architecture and detection for products, client/kernel/backend layers, memory, process, behavior, and input signals.
- Research and threats for analysis methods, bypass categories, platform interactions, protection, telemetry, and ethics.
- Repository map and repository resources for collection-backed source selection.
- Input provenance, detector operations, or network evidence for those specific evidence questions.
Use dma-attack-techniques, windows-kernel-security, graphics-api-hooking, mobile-security, or game-server-security when that boundary dominates. Apply game-security-research-rigor to consequential or disputed claims.