How to Scope a Pentest: The Information Your Tester Needs Before Quoting

Prepare the assets, user roles, access details, exclusions and deadlines your penetration tester needs to define scope and quote accurately.

A browser application and server enclosed by one translucent boundary representing an agreed penetration testing scope.

You ask three providers for a price and get three very different answers. One asks you a handful of questions, one sends a form, and one sends a number the same day. The reason is usually the same. Each provider is guessing at what you want tested. Good penetration testing scoping removes the guessing, and it helps you get a fair price for the right work.

This guide explains what scoping means, what information to gather, and how to hand it to a tester.

What Is Penetration Testing Scoping?

Scoping is the step where you and the tester agree on what will be tested, how deeply, and by when. It sets the boundaries of the work. It also lists what is out of bounds, such as a production database you cannot risk or a system owned by another company.

A clear scope protects both sides. The tester knows how much work to plan for. You know what the report will cover and what it will not.

What Are the Main Penetration Test Requirements?

Every provider asks for slightly different details, but the basic penetration test requirements are fairly consistent. Gather these before you ask for a price.

  • A list of assets. This means web applications, APIs, mobile apps, IP ranges, cloud accounts, and any internal networks you want tested.
  • The size of each asset. A site with five pages and a platform with hundreds of endpoints are very different jobs.
  • User roles. Say how many types of users can log in, such as customer, staff, and admin. Each role may need its own pass.
  • Test type. Tell the tester whether you want an outside-in test, an internal test, or both.
  • Your reason for testing. An audit, a customer request, a new launch, and a general check all shape the work in different ways.
  • Your timeline. Share any audit date, product release, or board deadline.

Why Does the Reason for the Test Matter?

A test for an ISO 27001 or PCI DSS audit needs a report that an auditor will accept. A test before a product launch needs fast results the developers can act on. Telling the tester the reason early helps them choose the right depth and the right report format.

If you are unsure, ask your auditor or customer what they expect to see. That one question can save you from paying for a retest later.

What Access and Background Should You Share?

Testers can work with no information, some information, or full information. Many teams share test accounts, a short description of how the system works, and a point of contact who can answer questions quickly.

More background usually means more of the budget goes into finding real problems rather than into guessing how the system behaves. If you plan to test a live system, say so, and agree on testing hours and a person to call if something breaks.

What Should You Leave Out of Scope, and Why?

List anything the tester must not touch. This may include third-party services you do not own, fragile legacy systems, or tests that could lock out real customers. Check with your cloud or hosting provider as well, because some have rules about what testing is allowed.

Write these limits down. Most disputes about pentests start with something that was assumed but never stated.

How Does Scoping Shape the Penetration Testing Quote?

A penetration testing quote is mostly an estimate of tester time, plus reporting and any retest. When your scope is vague, the provider has to add a safety margin, or the price may change halfway through the job. When your scope is clear, the quote is easier to compare and less likely to change.

Look for a quote that names the assets, the test type, the number of tester-days, what the report includes and whether a retest is part of the price. If any of those are missing, ask. A penetration testing quote that leaves them out is hard to compare with another.

What Should You Do Before You Ask for a Quote?

Run through this short list:

  • Write down every asset in plain language.
  • Mark which ones are live and which are test environments.
  • Decide who will answer the tester's questions.
  • Set up test accounts for each user role.
  • Note any dates that cannot move.

It takes a morning, and it will make the first conversation with a tester much more useful.

Why Talk to Penva Security About Your Pentest?

Penva Security offers web application, mobile application, API, network, and cloud penetration testing, as well as testing for AI and LLM systems. Its site includes an online quote calculator that gives an estimate based on a few scope questions. Fixed-price tests start from AUD 2,000 per engagement with a predefined scope. Penva describes a process of about one day for input, five to seven days for testing, one day for reporting, and one day for retesting. Reports use CVSS 3.1 severity scoring and can support audits such as ISO 27001, SOC 2, and PCI DSS, and a free retest is available within 60 days.

Before you request any penetration testing quote, take a moment to list your assets, user roles, and deadlines. Good penetration testing scoping costs you very little time, and it makes every quote you receive easier to trust.

Frequently Asked Questions

1. Can a provider quote without a scoping call?

Some can, especially for small fixed-scope tests. For anything larger, a short call or a form is usually needed so the quote fits your system.

2. What if I do not know every asset I own?

Say so. Many tester teams can include a discovery step, but it adds time. An internal list from your IT team is a good starting point.

3. How long does scoping take?

For a small test, it may take a day. Larger environments with several applications and networks can take longer, mainly because gathering information inside your own business takes time.

4. Can the scope change after the test starts?

It can, but changes usually affect time and price. Agree on how changes will be handled before work begins.

5. Do I need to tell my hosting or cloud provider?

Often, yes. Check the testing rules of any provider that hosts your systems, and get permission where it is needed.

CONTINUE THE CONVERSATION

Share this insight

Penva Security

← Back to all insights