security-audit

To find game security vulnerabilities before release, run a full security audit across save tampering, network exploitation, input validation, data exposure, and dependency supply chain risks to generate a prioritized remediation report.

A game security audit checks multiplayer codebases for network exploitation vectors, cheat prevention gaps, input validation issues, and data exposure risks, classifying each finding by severity to produce actionable fixes.

Yes, you can run a targeted security scan for save tampering risks by scoping the audit arguments to specific categories like save, network, or input validation instead of executing a full project audit.

To audit dependency supply chain risks in a game project, the security audit discovers source files via manifests and uses grep and glob evidence collection to identify vulnerabilities and classify their severity.

You should run a quick high-severity security scan during active iteration to rapidly check for critical vulnerabilities and ensure no open CRITICAL or HIGH items block your Polish to Release gate.