# Security setup What is already enforced in code, and what you still have to switch on in the Cloudflare dashboard. Every item ends with a command you can run to check it, because a security setting you believe is on and is not is worse than one you know is off. Companion docs: [`ADMIN.md`](ADMIN.md) for Access and the GitHub App, [`DEPLOYMENT.md`](DEPLOYMENT.md) for the Worker itself. --- ## 1. Response headers — done in code Three places now, and none inherits from the others: | File | Covers | |---|---| | `web/build/sveltekit-config.ts` (`csp`) | the Content-Security-Policy on every app page | | `web/static/_headers` | every other security header on static assets | | `web/worker/lib/http.ts` | everything the Worker generates (`/api/*`, `/img/*`) | Add a header that must hold everywhere and you must add it in each. ### Why the CSP moved out of `_headers` (2026-09-12) SvelteKit emits exactly one inline `