Vibe Coder · Unit 13: Testing and Security · Lesson 11 of 11

Security checklist

Engineers: a pre-launch review covering headers, dependencies, input handling, logging and an agent-assisted audit.

Read the short notes and pictures.Do everything inside a blue frame.

A pre-launch review

Security work is easier as a list. Go through each area once, record what you checked, and fix what you find. An agent audit is a useful extra pass, and its findings need verifying like any other.

A 3D scene of coloured blocks and cards. Areas: auth, access, input, secrets, dependencies, logs.
Auth, access, input, secrets, dependencies and logs.

The checklist

Auth and sessions

Provider-managed, secure cookies, sign-out works.

Access control

RLS on every table, server-side checks on every route.

Input

Validated on the server, output encoded, no string-built queries.

Headers and transport

HTTPS, sensible security headers.

Dependencies

Audited and pinned.

Logging

Useful, and free of secrets and personal data.

A 3D scene of coloured blocks and cards. An agent audit: fresh session, narrow brief, findings with file and line.
A fresh session with a narrow brief reports by file and line.

Running an agent audit

  1. Fresh context

    Not the session that wrote the code.

  2. One area at a time

    "Find missing authorisation checks."

  3. Demand evidence

    File, line and a way to reproduce.

  4. Verify before fixing

    Some findings will be false.

ActivityBuild stepA tested, locked-down app

Run the pre-launch review

Go through the checklist, run a dependency audit, and run an agent audit per area. Record findings, verify them, and fix everything of high severity.

Done when

Your app is tested and locked down, ready to deploy.

Keep these

  • Review by area.
  • Audit dependencies.
  • Verify agent findings before acting.