Checklist
Web Application Security Checklist for Product Teams
A practical list of areas to review before you ask for an external assessment.
How to use this checklist#
This is a starting point for internal review. It does not replace an independent assessment, but it helps you find obvious gaps first and makes any later test more productive.
Authentication and sessions#
- Passwords are stored with a modern, slow hashing algorithm.
- Login, password reset and signup are rate limited and do not reveal whether an account exists.
- Sessions expire, are invalidated on logout and password change, and cookies use
Secure,HttpOnlyand a suitableSameSitevalue. - Multi-factor authentication is available for sensitive roles.
Authorization#
- Every request is checked on the server against the user's role, organization and the specific object requested.
- Hidden buttons are never the only protection for an admin function.
- Tenants cannot read or change each other's data by changing an identifier.
Input and output handling#
- Database queries are parameterized.
- Output is encoded for the context where it is displayed.
- File uploads are restricted by type and size and are not served from an executable location.
Business logic#
- Prices, discounts, quantities and approvals are validated on the server.
- Multi-step flows cannot be skipped or replayed.
- Limits exist for expensive or abusable actions.
Operations#
- Secrets are not stored in source code or client bundles.
- Dependencies are tracked and updated.
- Security-relevant events are logged and someone reviews them.
- Error messages do not expose stack traces or internal details.
When most of these are in place, an assessment can spend its time on deeper logic and authorization problems instead of basic gaps.