Skip to content
← All work

Website security and backend Live

redteam.games

It started with a security audit of Red Team Interactive's site. Private reports were protected only in the browser, so Parker replaced that with a real server-side backend, which grew into a full staff platform for the studio.

Sign-in done properly

  • PBKDF2 password hashing, TOTP multi-factor sign-in with recovery codes, and Discord sign-in with PKCE
  • Hashed session tokens with timeouts, CSRF protection, and lockouts after repeated failed logins
  • The most sensitive actions need a fresh MFA check, and the database won't let staff approve their own moderation actions
The redteam.games boot screen.
The redteam.games boot screen.
The game library: Sail, Hard Drive, Monsters & Mazes and Monke Mages.
The game library: Sail, Hard Drive, Monsters & Mazes and Monke Mages.

Protecting what matters

  • A tamper-evident audit log: every entry is hash-chained, and database triggers block edits and deletes
  • Player personal data encrypted with AES-256-GCM envelope encryption. Viewing it takes a password, a TOTP code and a case reference, and it masks itself again after a minute
  • Uploaded images are checked and re-encoded, and attachments stay in quarantine until scanned
  • I-Spy telemetry must be HMAC-signed, with replay protection
  • A strict content security policy, and a deploy pipeline that fails if private reports can be reached without signing in

The role

Parker is Red Team Interactive's Lead Cybersecurity Contractor. The studio sponsors and fully endorses PZC Software.