RedFlag
All posts
·7 min read

A practical security checklist for shipping a Next.js app

A no-fluff checklist for securing a Next.js application before it goes live - auth, headers, secrets, dependencies, and the App Router gotchas that bite teams shipping fast.

Next.js makes it easy to ship an app in a weekend. It also makes it easy to ship a weekend's worth of security holes. This is the checklist we run through before calling a Next.js app production-ready.

Authentication & authorization

Secrets & configuration

Security headers

Set them in next.config. At minimum: a Content-Security-Policy, HSTS, X-Frame-Options (or frame-ancestors), X-Content-Type-Options, and a sensible Referrer-Policy. These are cheap and block whole classes of attacks.

Input handling

Webhooks & external requests

Dependencies & abuse

Verify it end-to-end

A checklist tells you what to look for; it doesn't tell you what you missed. Run a scan that reads the actual code - RedFlag will surface the specific routes, files, and lines where these rules are broken, ranked by how badly they can hurt you.

Find these bugs in your own repo

Paste a GitHub repo and RedFlag returns every vulnerability, ranked, with a one-click fix. Your first scan is free.

Scan your repo