ESSENTIAL GUIDANCE · SCOPING · 4 min read
Part of Validate insights →Defining your external penetration testing scope
A practical guide to setting targets, goals, exclusions and safe test rules for an external network penetration test.
Technical review lead: James Hinton · Offensive security lead
Need an acronym translated? Open the cyber glossary →
Summary
Define your external penetration testing scope by starting with the main question. Then confirm the authorised targets, exclusions, limits and test depth.
A good scope sets out ownership, access, permitted methods and safe limits so testers can work safely and produce useful evidence.
Agree the penetration test rules of engagement before testing begins, including reporting, escalation, remediation plans and retesting.
Start with the assurance question
An IP list names targets, but not the decision the test must support.
Clarify whether the objective is to assess a new perimeter, investigate exposure identified by monitoring, support customer assurance, or test whether an attacker can reach a specific service.
The goal drives the depth, tester skills, evidence and reporting detail required. It also stops a wide scope from giving shallow answers.
Build an accurate target list
Include public IP ranges, domains, subdomains, services reachable from outside, cloud endpoints, VPN gateways and relevant third-party-hosted components that you are explicitly authorised to test.
Identify asset owners and live dependencies.
Also separate customer-owned systems from supplier infrastructure.
External discovery can help find missed assets, but each target still needs confirmed ownership and explicit written authorisation from the relevant system owner before active testing begins.
Define exclusions and operational constraints
List services that must not be tested, prohibited techniques, data-handling rules, test accounts, test windows, rate limits and production-safety needs.
Agree how critical findings will be escalated and who can pause the work.
Clear limits do not weaken the test; they let testers investigate with confidence within agreed operational safeguards.
Choose depth on purpose
A vulnerability assessment gives broad, repeatable coverage of known issues.
Penetration testing adds expert investigation, validation and controlled exploitation to demonstrate attack paths within the agreed scope.
Black-, grey- and white-box approaches define different starting knowledge and access. Their value depends on the objectives and available testing effort.
Choose the method that best answers the business question, rather than holding back context just to make the test seem more real.
Agree outputs and retesting before work starts
State how findings will be shared, the technical evidence and severity rationale required, the report audience, remediation guidance and whether retesting is included.
Pentesys Validate keeps the agreed scope, live findings, evidence, owners and closure status linked in the Portal.
The pricing calculator can give an indicative starting point, but technical scoping sets the final effort and quote.
External vs internal penetration testing
External testing checks agreed internet-facing systems from an outside starting point.
Internal testing checks agreed systems and trust boundaries from an internal or assumed-access point.
They answer different questions.
A public-facing service can connect to internal identities or apps, but an external test does not automatically authorise testing of every connected system.
State where the test begins, which boundaries can be crossed and what stays out.
Choose black-, grey- or white-box access for the goal
Agree the information and access the tester will get instead of using the label alone.
- Black box: little or no advance knowledge or access, good for an agreed outside-in question.
- Grey box: selected information or accounts to test defined roles and access limits.
- White box: extensive agreed information, such as architecture or source access where it helps, for deeper review.
These labels describe starting knowledge and access, not full coverage.
External testing can include authenticated testing where explicitly scoped.
Record accounts, roles, permissions and exclusions in the engagement.
Use a commissioning checklist
- Confirm target ownership and explicit written authorisation.
- Record IPs, domains, services, environments and exclusions.
- State the starting point, supplied accounts and allowed attack paths.
- Agree production limits, escalation contacts and stop conditions.
- Specify evidence, reporting, remediation guidance and retest plans.
Use discovery findings to improve the list, then confirm explicit written authorisation from the relevant system owner before adding a newly found asset to active testing.
Use the penetration test scoping guide and editable workbook to record objectives, targets, exclusions, responsibilities and final approval.
Q&A
Does external penetration testing include internal systems?
Only where the agreed scope and explicit written authorisation explicitly permit that activity.
Clearly state whether internal testing or movement across a boundary is included instead of assuming it follows from an external test.
Is external penetration testing always black box?
No.
External describes the starting point and target exposure.
Black, grey and white box describe the information and access supplied.
Choose and document both to match the assurance goal.





