Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 38 ยท Scoping, Rules and Methodology

Scoping a Penetration Test

Learn how to scope a penetration test: asking the client the right questions, defining targets and exclusions, estimating effort, setting objectives and avoiding scope creep.

Scoping is the conversation that decides what will be tested, how deeply, by whom and when. It happens before any technical work, and it quietly determines whether the engagement succeeds. A vague scope leads to missed systems, surprise outages, arguments about cost and, in the worst case, testing something you had no right to touch. A good scope turns a client's worry ("are we safe?") into a precise, testable plan.

Why scoping matters

Think of the scope as the contract between what the client expects and what you will deliver. It protects both sides:

  • The client knows what they are paying for and what the limits are.
  • The tester has legal cover and a clear definition of done.
  • Everyone agrees on risks to production systems in advance.

Start with objectives, not targets

Ask what the client wants to learn. Clients rarely say it directly. Useful starting questions:

  1. Why now? A compliance deadline, a new product, a recent incident?
  2. What would hurt most if it were lost or stopped?
  3. Which threat worries you: outsiders, insiders, suppliers?
  4. What was tested before, and what was found?
  5. Who must be told about the test, and who must not?

Objectives translate to success criteria, such as "demonstrate whether an external attacker can reach customer records" or "confirm that the new payment flow resists tampering".

Scoping conversation

Why Goals and drivers.
What Targets and exclusions.
When Windows and duration.
Who Contacts and approvers.

Answers feed the statement of work.

1 / 2

What a scope document contains

Item Examples
In-scope assets 192.0.2.0/28, app.example.test, the iOS app v3.2
Out-of-scope assets Payment processor, hr.example.test, shared hosting neighbors
Test type and depth Grey box, authenticated, no denial-of-service
Allowed techniques Phishing yes or no, physical entry yes or no
Time window 09:00 to 17:00 UTC on weekdays, or nights only
Test accounts Two normal users and one admin
Source addresses Tester IPs, so the client can recognize them
Contacts Technical lead and an emergency 24-hour number
Deliverables Report format, readout meeting, retest included?
Legal terms Liability, confidentiality, data handling

The client should state ownership of every in-scope item. Treat "everything" as a red flag: ask for a list.

Defining targets precisely

Be explicit and unambiguous.

  • Use CIDR ranges and exact host names, not "our network".
  • State whether new assets found during the test are in scope. Many agreements say that discovered hosts are in scope only if they are provably owned by the client and approved by a named contact.
  • List exclusions such as fragile legacy systems, production databases during business hours, or third-party services.
  • Say whether subdomains are included: a wildcard like *.example.test can include dozens of hosts, some belonging to vendors.

Estimating effort

Effort drives price and calendar time. Typical inputs:

  • Number of IP addresses or live hosts.
  • Number of web applications, with their size (pages, roles, API endpoints).
  • Depth: automated plus light manual, or deep manual.
  • Authenticated or not; number of user roles to test.
  • Reporting and retest effort, which is often 20 to 30 percent of the total.

A simple model: base days per item, multiplied by a depth factor, plus reporting. The result is an estimate to discuss, not a promise. Always leave a margin for the unexpected.

Scope creep

During testing, the client may say "while you are there, can you also look at the HR portal?" Resist the urge to say yes on the spot. New systems need the same ownership checks, risk review and paperwork. Use a change request: write down the addition, confirm approval from a person who can authorize it, and update the scope document. Verbal approval in a hallway does not protect you.

Stand-in: an effort estimator

The first example builds an estimate from the scope items. The numbers are invented and illustrate the method only.

Python Estimate engagement days

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second example is a scope-document linter. It reads a scope as data and warns about the vague wording and missing items that cause trouble later.

Python Lint a scope document

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Questions to ask before saying yes

  • Are there systems that cannot tolerate scanning or load?
  • Is there monitoring, and should it be told? (Some clients want the blue team unaware to test detection; most want a trusted contact informed so a real incident is not confused with your test.)
  • Are backups current in case something breaks?
  • Is data in scope regulated (health, payment, personal)?
  • What happens if you find evidence of a real, ongoing intrusion? Agree in advance to stop and call the emergency contact immediately.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What should drive the scope of a test?

    Objectives decide which assets matter, how deep to go and what success means.
  2. 2. A client says 'test our network'. What is the best reaction?

    Vague scope is a legal and practical risk. Get an explicit list and ownership confirmation.
  3. 3. Halfway through, the client asks you to also test another system. What do you do?

    New systems need ownership checks and updated paperwork, like the original scope.
  4. 4. Why should you ask about backups before testing?

    Even careful testing carries some risk to fragile systems, so recovery readiness matters.

Summary

  • Scoping defines what, how deep, when and who. It protects client and tester.
  • Start with objectives, then list exact targets, exclusions, techniques, windows, accounts and contacts.
  • Treat vague words such as "everything" as warnings; confirm ownership of each asset.
  • Estimate effort from asset counts and depth, including reporting and retest.
  • Handle additions through written change requests, not hallway agreements.

Next: Rules of Engagement