Security and reliability prompts for coding agents
Attention brings attackers and load as well as users. These prompts close the obvious doors before launch day.
- Security and reliabilitySecurity headers and HTTPS, set once for every responseSet HSTS, CSP, framing, MIME and referrer headers on every response, with CSP rolled out without breaking the site.45 to 90 minutes
- Security and reliabilityHarden sign-up, login and password resetCheck how passwords, sessions and resets work, and fix the gaps attackers try first.1 to 2 hours
- Security and reliabilityScan for leaked secrets and lock them downFind API keys and passwords in the code, the history and the browser bundle, and stop new ones getting in.30 to 60 minutes
- Security and reliabilityRate limits on public endpointsLimit how often anyone can hit the endpoints that cost money or invite abuse, with clear 429 answers.45 to 90 minutes
- Security and reliabilityError tracking, health checks and uptime alertsKnow about errors and outages before your users tell you: error tracking, a health endpoint and alerts.45 to 90 minutes
- Security and reliabilityDatabase backups you have actually restoredMake sure your data is backed up on a schedule, kept long enough, and that a restore actually works.45 to 90 minutes