All articlesSecurity Strategy

Web Application Security Testing Checklist (2026)

Updated November 17, 2026·69 checks·Mapped to the OWASP Top 10:2025·Nautillo Pro Security Team

Most vulnerabilities in production web apps were already there at launch — and never found. This checklist covers the checks that matter before you ship and after every major release: 69 checks organised by the OWASP Top 10:2025, each with how to test it, a severity rating, and whether it can be automated.

Quick answer

A web application security testing checklist should cover access control (IDOR, privilege escalation, SSRF), security configuration and headers, outdated components, TLS and secrets, injection (SQL, XSS, command, template), business logic, authentication and sessions, file uploads and integrity, logging, error handling, and API security. Fix Critical items first, automate the externally testable (DAST) checks so they run on every release, and review the rest in code and configuration.

Download the checklist

Print-ready PDF with tick boxes, or a spreadsheet to track progress with your team. Free to use and share.

How to use this checklist

Work through each category. Critical items are what attackers look for in the first minutes of probing an application — fix these first. High items have direct security impact and should be resolved before launch. Medium items need specific conditions to exploit; Low items are hardening.

DAST checks can be tested automatically from outside against your running application, so they can run on every release. Review checks need a look at code, configuration or process. Only test applications you own or are authorized to test.

Jump to: Access Control · Security Misconfiguration · Software Supply Chain & Components · Cryptography & Data Protection · Injection · Insecure Design & Business Logic · Authentication & Sessions · Software & Data Integrity · Logging & Alerting · Error Handling & Exceptional Conditions · API Security

Access Control

A01:2025 Broken Access Control

Every endpoint checks that the logged-in user owns the record it returns or changes (no IDOR)

How to test: Log in as user A, request user B's object by changing the ID in the URL, body or query — expect 403/404

CriticalDAST

Admin-only functions are blocked for regular users

How to test: Call admin URLs and API routes with a normal user's session — expect 403

CriticalDAST

Authorization is decided on the server, never from client-supplied roles or flags

How to test: Tamper with role, isAdmin or plan fields in requests, cookies and tokens; the response must not change

CriticalDAST

Users cannot raise their own privileges by adding fields to update requests (mass assignment)

How to test: Add role, is_admin or owner_id to a profile update request and check whether it is stored

CriticalDAST

Deleted or deactivated users lose access immediately

How to test: Deactivate a test user, then replay one of their earlier requests and session

HighDAST

Server-side requests cannot be pointed at internal addresses (SSRF)

How to test: Submit URLs to 127.0.0.1, private ranges and 169.254.169.254 in URL-fetching features — they must be refused

CriticalDAST

Multi-tenant data is filtered by tenant on every query

How to test: Review data-access code for a tenant filter; test cross-tenant IDs with two test accounts

CriticalReview

Security Misconfiguration

A02:2025 Security Misconfiguration

Security headers set: Content-Security-Policy, X-Frame-Options or frame-ancestors, X-Content-Type-Options, Referrer-Policy

How to test: Inspect response headers on key pages (curl -I or browser dev tools)

MediumDAST

HSTS enabled so browsers always use HTTPS

How to test: Check for a Strict-Transport-Security header with a long max-age

HighDAST

CORS does not reflect arbitrary origins or allow '*' with credentials

How to test: Send a request with Origin: https://evil.example and check Access-Control-Allow-Origin / -Credentials

HighDAST

Debug mode, verbose error pages and framework consoles are off in production

How to test: Trigger errors (bad input, unknown routes) and look for stack traces, framework names or debug toolbars

MediumDAST

Directory listing is disabled

How to test: Request folders such as /uploads/ or /static/ and check for an index of files

MediumDAST

No exposed .git, .env, backup or config files

How to test: Request /.git/HEAD, /.env, /backup.zip, /config.json and similar predictable paths

CriticalDAST

Default credentials changed on every admin panel, database and service

How to test: Inventory admin interfaces and try vendor default logins in a test environment

CriticalReview

Admin and internal interfaces are not reachable from the public internet

How to test: Scan for /admin, management ports and internal dashboards from outside your network

CriticalDAST

Cloud storage buckets are private unless intentionally public

How to test: Review bucket policies; try anonymous listing of known bucket names

CriticalReview

Forgotten staging, preview and test environments are removed or protected

How to test: Enumerate subdomains (certificate transparency logs) and check each is still needed and protected

MediumReview

Software Supply Chain & Components

A03:2025 Software Supply Chain Failures

No end-of-life server software, frameworks or runtimes in production

How to test: Fingerprint versions from headers and responses; compare with vendor end-of-life dates

HighDAST

No dependencies with known exploited vulnerabilities (CISA KEV) or critical CVEs

How to test: Run a dependency audit (npm audit, pip-audit, Dependabot) in CI and fix or pin

HighReview

Third-party scripts loaded with Subresource Integrity (SRI) or from your own origin

How to test: Check <script> tags from CDNs for integrity= attributes

MediumDAST

Lockfiles committed and builds reproducible

How to test: Confirm package-lock / poetry.lock / go.sum are in the repository and used in CI

MediumReview

CI/CD secrets are scoped, rotated and never printed in logs

How to test: Review pipeline variables, permissions and recent build logs

HighReview

Cryptography & Data Protection

A04:2025 Cryptographic Failures

TLS 1.2 or 1.3 only, with a valid certificate and strong ciphers

How to test: Run a TLS scan (e.g. testssl.sh) against every public hostname

CriticalDAST

No authenticated page or API is served over plain HTTP

How to test: Request http:// versions of login and API URLs — expect a redirect to HTTPS

CriticalDAST

Passwords hashed with Argon2, bcrypt or scrypt — never MD5, SHA-1 or plain SHA-256

How to test: Review the password storage code and a sample of stored hashes

CriticalReview

Secrets, API keys and connection strings are not in code, the repository or the frontend bundle

How to test: Run a secret scanner (gitleaks, trufflehog) on the repo and search built JavaScript for keys

CriticalReview

Sensitive data encrypted at rest where required (backups, personal data)

How to test: Review database, storage and backup encryption settings

HighReview

API responses return only the fields the client needs

How to test: Inspect list and detail API responses for hidden fields (emails, hashes, internal IDs)

HighDAST

Injection

A05:2025 Injection

SQL queries use parameterized statements — no string concatenation

How to test: Send ' and " and time-based payloads to inputs and watch for errors or delays

CriticalDAST

NoSQL queries reject operator injection

How to test: Send {"$ne": null} or {"$gt": ""} in JSON fields used for lookups and login

CriticalDAST

User input is output-encoded in HTML, attributes and JavaScript (no XSS)

How to test: Submit a unique marker with <, >, " and ' to every input and check how it is reflected or stored

HighDAST

No DOM-based XSS from URL fragments, query parameters or postMessage

How to test: Review client code for innerHTML, document.write and eval fed by user-controlled sources

HighReview

OS commands never include user input without a strict allowlist

How to test: Send time-based payloads (; sleep 5) to inputs that may reach shell commands, in a test environment

CriticalDAST

Template engines never render user input as template code (no SSTI)

How to test: Submit {{7*7}}, ${7*7} and <%= 7*7 %> — the response must not show 49

CriticalDAST

XML parsers have external entities disabled (no XXE)

How to test: Send an XML body with an external entity reference to XML-accepting endpoints

HighDAST

Redirect targets are validated against an allowlist (no open redirect)

How to test: Set redirect / next / url parameters to an external domain and follow the response

MediumDAST

Insecure Design & Business Logic

A06:2025 Insecure Design

Prices, quantities and discounts are calculated on the server

How to test: Change price, quantity or discount values in checkout requests — negative and zero values too

CriticalDAST

Multi-step workflows cannot be skipped or replayed

How to test: Call the final step of a flow (payment confirmation, approval) directly, or twice

HighDAST

Race conditions cannot duplicate one-time actions (coupons, credits, withdrawals)

How to test: Send the same request 10–20 times in parallel and compare the result with a single request

HighDAST

Expensive or sensitive actions are rate-limited (sign-up, password reset, exports, SMS)

How to test: Repeat the action rapidly and confirm throttling kicks in

MediumDAST

Threat model reviewed for new features that handle money, permissions or personal data

How to test: Run a short abuse-case review before release: 'how could a user misuse this?'

MediumReview

Authentication & Sessions

A07:2025 Authentication Failures

Login is rate-limited and protected against brute force and credential stuffing

How to test: Send many failed logins quickly and check for throttling, lockout or CAPTCHA

HighDAST

Login errors don't reveal whether an account exists

How to test: Compare responses and timing for a real vs a non-existent email

MediumDAST

Session tokens are long, random and unpredictable

How to test: Collect several session IDs and check for patterns or short length

CriticalDAST

Session cookies use HttpOnly, Secure and SameSite

How to test: Inspect Set-Cookie headers after login

HighDAST

Logout and password change invalidate the session on the server

How to test: Reuse an old session token after logout or a password change — expect 401

HighDAST

Password reset tokens are single-use and expire within an hour

How to test: Reuse a reset link, and use one after expiry — both must fail

HighDAST

JWTs are verified for signature, algorithm and expiry (no alg:none, no weak secret)

How to test: Send a token with alg set to none, an expired token and a tampered payload — all must be rejected

CriticalDAST

MFA is available for admin and privileged accounts

How to test: Review admin account settings and enforce MFA for privileged roles

MediumReview

OAuth / SSO redirect URIs are exact-match and state is validated

How to test: Try modified redirect_uri values and a missing or reused state parameter

HighDAST

Software & Data Integrity

A08:2025 Software or Data Integrity Failures

File uploads validate type on the server and store files outside the web root

How to test: Upload a script file renamed to .jpg and a double-extension file, then try to request and execute them

CriticalDAST

Uploaded filenames are replaced or sanitized

How to test: Upload files named ../../evil.txt or with special characters and check where they land

HighDAST

No unsafe deserialization of user-controlled data

How to test: Review code for pickle, Java serialization, PHP unserialize or YAML load on request data

CriticalReview

Incoming webhooks verify a signature before acting

How to test: Send an unsigned or wrongly signed webhook request — it must be rejected

HighDAST

Deployments come only from the CI pipeline with reviewed code

How to test: Review who can deploy to production and whether branch protection is enforced

MediumReview

Logging & Alerting

A09:2025 Security Logging & Alerting Failures

Logins, failed logins, permission changes and admin actions are logged

How to test: Perform these actions in staging and confirm a log entry with user, time and IP

MediumReview

Alerts fire on suspicious patterns (brute force, mass data export, many 403s)

How to test: Simulate the pattern in staging and confirm someone is notified

MediumReview

Logs never contain passwords, tokens, keys or full card numbers

How to test: Search recent application logs for secrets and personal data

HighReview

Logs are retained long enough to investigate an incident and protected from tampering

How to test: Review retention settings and who can delete or edit logs

LowReview

Error Handling & Exceptional Conditions

A10:2025 Mishandling of Exceptional Conditions

Errors return generic messages — no stack traces, SQL errors or internal paths

How to test: Send malformed JSON, wrong types and oversized values and read the error bodies

MediumDAST

Failures fail closed — an error in an auth or payment check denies the action

How to test: Review error branches in authorization and payment code; test with a dependency unavailable in staging

HighReview

Request size, upload size and timeouts are limited

How to test: Send very large bodies and slow requests and confirm they are rejected

MediumDAST

Unhandled exceptions don't leave partial state (half-created orders, double charges)

How to test: Interrupt multi-step operations in staging and check data consistency

MediumReview

API Security

OWASP API Security Top 10

Every API endpoint requires authentication unless it is intentionally public

How to test: Replay API calls without a token and with another user's token

CriticalDAST

APIs are rate-limited per user and per IP

How to test: Send bursts of requests and confirm 429 responses

HighDAST

GraphQL introspection is disabled in production

How to test: Send an introspection query (__schema) to the GraphQL endpoint

MediumDAST

GraphQL query depth, complexity and batching are limited

How to test: Send deeply nested and batched queries and check they are rejected

MediumDAST

Old API versions and undocumented endpoints are retired

How to test: Compare live routes (e.g. /api/v1, /api/internal) with your API documentation

MediumDAST

API keys are scoped, rotatable and never sent in URLs

How to test: Review key permissions and search logs and URLs for keys in query strings

HighReview

What this checklist doesn't cover

A checklist tests for known patterns. It won't find vulnerabilities specific to your application's business logic — a price manipulation flaw in your checkout, a workflow bypass in your approval process, or an access control gap that only makes sense given how your users are structured. For deeper coverage, see the OWASP Web Security Testing Guide (WSTG) and the Application Security Verification Standard (ASVS).

Checklist

Known patterns, configuration checks, code review items. Fast to run, easy to understand.

Misses novel chains and business logic

Automated testing (DAST)

Actively attempts exploit paths on every release and confirms impact with HTTP evidence.

Limited on bespoke business logic

Manual pentest

Human reasoning across trust boundaries, creative chaining, compliance-grade reports.

Expensive, point-in-time only

Keep a copy

Use the PDF for a pre-launch review, or the spreadsheet to assign checks and track fixes.

Frequently asked questions

Is there a web application security testing checklist PDF?

Yes — this checklist is available as a free, print-ready PDF with tick boxes, and as a CSV you can open in Excel or Google Sheets to assign checks and track fixes. Both contain all 69 checks with how to test each one, severity and whether it can be automated.

What should a web application security testing checklist include?

At minimum: access control (IDOR, privilege escalation, SSRF), security configuration and headers, outdated components and supply chain, TLS and secrets handling, injection (SQL, NoSQL, XSS, command, template), business logic, authentication and sessions, file uploads and integrity, logging and alerting, error handling, and API security.

Is this checklist based on OWASP?

Yes. The categories follow the OWASP Top 10:2025, plus a section from the OWASP API Security Top 10. For deeper, test-by-test coverage use the OWASP Web Security Testing Guide (WSTG) and the Application Security Verification Standard (ASVS).

Which security checks can be automated?

Checks marked DAST can be tested automatically from outside against the running application — injection, access control, authentication, headers, TLS, exposed files and more — so they can run on every release. Checks marked Review need code, configuration or process review, such as password hashing, secrets in the repository or logging.

How often should I run a security testing checklist?

Run the full checklist before launch and after major changes, and automate the DAST checks so they run on every release. Review the manual items at least quarterly and whenever you add features that handle money, permissions or personal data.

Run the DAST checks automatically — on every release

Nautillo Pro runs the externally testable checks against your live application and proves every confirmed finding with the exact request and response. The free plan covers passive checks plus 1 active attack scan a month on a verified domain; Professional runs the active attacks — injection, access control, authentication and more — on every release, with the CI/CD API.

Related articles