security-audit

To find and fix game security vulnerabilities before release, run a full-mode security audit to scan for save tampering, multiplayer cheat vectors, data exposure, and input validation gaps, generating a prioritized remediation report.

A pre-release security gate blocks public release when CRITICAL or HIGH findings remain in the audit. It validates Polish → Release readiness by requiring resolution of identified multiplayer exploit paths and data exposure risks.

Yes, you can run a targeted security audit for multiplayer cheating risks by using network-scoped mode. This isolates network exploit paths and multiplayer cheat vectors without scanning save tampering or input validation categories.

The best way to audit save tampering and input validation gaps is executing save and input-scoped security audits. These modes identify unsafe input handling and save file exploit paths, producing severity-ordered remediation guidance.

A game security audit evaluates dependency inventory alongside data exposure and network exploit paths. It scans the codebase for common security failures across multiple categories to ensure comprehensive pre-release readiness.

You should not use a full security audit scan when time is constrained or targeting a specific feature update; instead, use quick scope for rapid checks or network scope when following up on disk and network-using features.