Penetration testing

How to scope a penetration test (and avoid paying for the wrong one)

Most disappointing pen tests were scoped wrongly — too narrow, aimed at the wrong system, or missing the access testers needed. Ten minutes of preparation before the scoping call makes a big difference.

Start with the question you need answered

For example:

  • “Our bank partner wants evidence the customer app and API are secure.”
  • “If an attacker phished one employee, could they reach client data?”
  • “We’re launching a new portal and want it tested first.”
  • “Our insurer or ISO 27001 auditor wants an annual external test.”

The question determines the test type, the starting point and how the results are reported.

What to prepare by test type

Web applications

  • URLs and environments — and whether staging matches production.
  • The number of user roles, with a test account for each.
  • A rough count of pages, functions and workflows, and which areas are sensitive.
  • Any WAF or rate limiting that needs allow-listing.

APIs

  • Documentation — an OpenAPI/Swagger file or Postman collection.
  • The number of endpoints and the authentication method.
  • Test credentials or keys for each role.

External infrastructure

  • The IP ranges and domains you own, including cloud-hosted assets.
  • Confirmation of your authority to test, including your hosting provider’s rules.

Internal and assumed breach

  • The approximate number of hosts and sites.
  • The starting point — a standard laptop, a VPN account or a tester-provided VM.
  • Any fragile or out-of-bounds systems.

Cloud

  • Providers, and the number of accounts or subscriptions.
  • Read-only access for configuration review — and whether attack-path testing is wanted.

Rules of engagement

Agree in writing: the in-scope targets, testing windows, emergency contacts, anything off-limits (denial of service, social engineering, changes to production data) and how critical findings will be reported during testing.

Common scoping mistakes

  • Testing the marketing site instead of the application.
  • Unauthenticated-only testing of an authenticated product.
  • Leaving out the API the mobile app uses.
  • Forgetting third-party hosted components you’re responsible for.
  • Cutting days to fit a budget, so the test only skims the surface.

The bottom line

A good scope is short, specific and tied to a business question. You should leave the scoping call with a fixed price and a clear statement of what will — and won’t — be tested.

Frequently asked questions

What information is needed to scope a pen test?

The business question, target URLs, IPs or cloud accounts, the number of user roles and test accounts, API documentation, testing windows, out-of-scope systems and emergency contacts.

Want help scoping?

Fixed-price testing, scoped and delivered by a senior tester, with live findings on the SMARTSEC client platform.