Skip to content
← All articlesEngineering

Web Application Security Checklist Based on the OWASP Top 10

A practical web application security checklist for CTOs and product managers, built around the OWASP Top 10 risks, with what to ask your development partner.

Most serious web application breaches do not come from exotic attacks. They come from familiar mistakes: a missing permission check, an unpatched library, a secret committed to a repository. The OWASP Top 10, published by the Open Worldwide Application Security Project, is a widely used awareness list of the most common web application risk categories. It is a good shared vocabulary between a product owner and an engineering team.

This checklist turns those categories into questions you can ask, and evidence you can expect, whether your team is in-house or outsourced. Category names and ordering change between OWASP editions, so treat the themes below as the durable part.

Why a checklist, not a one-off audit

A penetration test at launch is useful, but it is a snapshot. Security depends on daily habits: how code is reviewed, how dependencies are updated, how environments are configured. A checklist makes those habits visible and repeatable, and it gives you something concrete to put in a statement of work.

The checklist

1. Access control

Broken access control is consistently near the top of the OWASP list. It means a user can see or change something they should not.

  • Authorisation is enforced on the server for every request, never only by hiding buttons in the interface.
  • Users cannot access another user’s record by changing an ID in the URL or request body.
  • Admin functions are separated and protected by role checks.
  • Default stance is deny: new endpoints require an explicit permission rule.

2. Cryptography and data protection

  • All traffic uses HTTPS, with HTTP redirected.
  • Passwords are stored with a purpose-built slow hashing algorithm such as Argon2, bcrypt or scrypt, never in plain text or with a fast general-purpose hash.
  • Sensitive data at rest, such as backups and database volumes, is encrypted.
  • You collect only the personal data you need, and you know where it is stored.

3. Injection

SQL, command and template injection happen when untrusted input is treated as code.

  • Database access uses parameterised queries or a well-maintained ORM, not string concatenation.
  • Input is validated on the server for type, length and format.
  • Output is encoded for its context to prevent cross-site scripting, and a Content Security Policy is considered.

4. Secure design

Some flaws cannot be fixed by careful coding because the design allows them.

  • Threat modelling happens for sensitive features such as payments, password reset and file upload.
  • Rate limits exist on login, search and any expensive endpoint.
  • Business rules, such as “a refund cannot exceed the payment”, are enforced in code, not assumed.

5. Configuration

  • Debug modes, sample accounts and verbose error pages are off in production.
  • Cloud storage buckets and databases are not publicly reachable unless intentionally so.
  • Security headers are set, and unused services and ports are closed.
  • Environments are defined as code so configuration drift is visible. See our infrastructure as code guide.

6. Dependencies

  • A dependency scanner runs in the build pipeline and fails on serious known vulnerabilities.
  • Libraries are updated on a schedule, not only when something breaks.
  • Lockfiles are committed, and the team knows which packages the application actually uses.

7. Authentication

  • Multi-factor authentication is available, and required for administrators.
  • Session tokens expire, rotate on login and are invalidated on logout.
  • Password reset links are single-use and time-limited.
  • Where possible, use a proven identity provider or framework rather than building login from scratch. Our guide to authentication for web and mobile apps covers the options.

8. Integrity of software and data

  • Builds come from a controlled pipeline, not a developer laptop.
  • Third-party scripts loaded in the browser are reviewed and kept to a minimum.
  • Deserialising untrusted data is avoided or tightly restricted.

9. Logging and monitoring

  • Logins, failed logins, permission failures and administrative actions are logged.
  • Logs never contain passwords, tokens or full card numbers.
  • Someone is alerted when unusual patterns occur, and there is a written incident response contact list.

10. Server-side requests

  • If the application fetches URLs supplied by users, such as webhooks or image imports, it validates destinations and blocks internal network addresses.

What good evidence looks like

When you ask a vendor whether they follow these practices, a yes is not enough. Ask for artefacts.

Area Evidence to request
Code review Pull request history showing security-minded review
Dependencies Scanner output in the CI pipeline
Access control Automated tests that try to access another user’s data
Configuration Infrastructure code and environment documentation
Logging A sample of audit logs with sensitive fields masked
Testing Latest penetration test summary and remediation status

Where security fits in the delivery process

Security is cheapest when it starts early. Add security acceptance criteria to user stories, run static analysis and dependency checks on every commit, and schedule an independent penetration test before major launches and after large changes. Pairing these with code review practices for outsourced teams means issues are caught while the context is still fresh.

A note on responsibility

No checklist guarantees a system is secure. It reduces the likelihood and impact of common failures. Regulations such as GDPR may also apply depending on your users and data, so involve legal or compliance advisers where needed.

Next steps

If you want a team that builds these checks into every sprint, our web development services include secure coding practices, and our software testing services can add independent security-focused test coverage. To review your current application against this checklist, contact us and we will walk through it with you.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.