How to scope a web application penetration test

The decisions that set the quality of a test before it starts: roles, tenants, environments and limits.

Web page source code on a blue screen

Why scope matters more than hours

Two tests with the same number of days can produce very different results. The difference is usually scope: which parts of the product were tested, with which accounts, in which environment. A clear scope also lets you compare proposals from different providers on equal terms.

Start from what the reader of the report needs

If an enterprise customer asked for the test, scope the product and APIs they will use. If it supports an audit, include the systems inside the audit boundary. Writing down who will read the report prevents a test that is technically sound but answers the wrong question.

List roles and tenants, not just URLs

Most serious web application findings are about access: one user, role or customer reaching what belongs to another. A tester needs accounts to find them. Plan for:

  • Two accounts for each role in scope, such as viewer, editor and administrator.
  • Accounts in two separate tenants or organisations, if your product is multi-tenant.
  • Any support, partner or internal roles that can see customer data.

Include the APIs and integrations behind the screens

Modern applications call APIs that can be reached directly. Include the API hosts the web application uses, file upload and export features, webhooks and single sign-on. Name third-party services you rely on but do not own; they are usually out of scope unless their owner agrees in writing.

Choose the environment

A staging environment with realistic data is usually safest and lets testers try actions that would be disruptive in production. If you test production, agree hours, rate limits and actions to avoid, such as sending emails to real customers.

What a provider needs to quote

To get an accurate proposal, share:

  • A short description of the application and its users.
  • The number of roles, and whether it is multi-tenant.
  • Roughly how many distinct pages, functions or API endpoints it has.
  • The environment to test and any testing windows.
  • Your deadline and who will read the report.

Leave room for the retest

Book the test early enough to fix high and critical findings and have them retested before your deadline. A report that shows findings as fixed and verified carries more weight with reviewers than one listing open issues.

Sources

General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.

Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.