ESSENTIAL GUIDANCE · BUYER GUIDE · 5 min read

Part of Validate insights →

How to scope and prepare for a penetration test without missing critical systems

A practical method for defining penetration-test scope and preparing assets, access, monitoring, approvals and rules of engagement.

Business review lead: Mathew Colley · Sales Director

Start with the business services and risks that need assurance. Map the systems, identities, APIs, cloud resources and third-party dependencies that support them, then document what is included, excluded and assumed, how testing may proceed and how newly discovered assets will be handled.

Need an acronym translated?Open the cyber glossary →

Define the assurance question

State what the organisation needs to learn or protect: whether an unauthenticated user can reach customer data, whether a normal user can cross a tenant or privilege boundary, whether a major release introduced exploitable paths, or whether agreed fixes address previously demonstrated findings. The answer determines the assets, identities, techniques and evidence the engagement needs.

Map the business service and its dependencies

Map the domains, IP ranges, applications, APIs, cloud resources, identity providers, data stores, remote-access services and third-party dependencies that support each important user journey. Reconcile asset-management records with DNS, certificate, cloud, identity, supplier and recent-change records. If the inventory is incomplete, say so and agree whether discovery forms part of the engagement.

Include identities, roles and business flows

List the roles and trust decisions that need testing, including unauthenticated users, ordinary users, administrators, service accounts, separate customer tenants and third-party integrations. Identify high-impact flows such as account recovery, payment, data export, approval and privilege change. Provide representative test accounts where they can be used safely.

Define the authorised scope precisely

Record applications, APIs, domains, IP ranges, cloud environments, user roles and test environments, together with exclusions, constraints and assumptions. Every active target requires explicit written authority from its owner; a supplier relationship, passive external visibility or technical reachability does not create permission to test a third party. For each material exclusion, record the untested risk it leaves.

Agree rules of engagement

Set the authorised targets and scope version, testing windows, source addresses, permitted and prohibited techniques, data-handling requirements, escalation contacts, stop conditions and change-control route. Explain how critical findings and potential service impact will be handled. These controls make meaningful investigation safer without reducing the work to a superficial checklist.

Independent guidance:Read the NCSC penetration-testing guidance →

Allocate responsibilities and prerequisites

State who will provide test accounts, architecture information, allow-listing, test data, access and internal approvals; who will monitor the environment; and who has authority to pause or extend testing. Record dependencies, lead times and what happens if prerequisites are late or incomplete. Clear responsibilities protect the schedule, commercial assumptions and safety of the engagement.

Prepare access, context and test data

Provide dedicated accounts for the roles and boundaries in scope, agree how credentials will be transferred and removed, and confirm VPN routes, source-address allow-listing, client certificates and other access prerequisites before the test window. Supply useful architecture, data-flow, API and permission information. Use representative non-production data where possible and minimise any sensitive evidence needed to demonstrate a finding.

Prepare monitoring and recovery

Confirm who will monitor service health and security alerts, what telemetry should be retained, who can isolate an account or service and how an unexpected incident will be handled. Check appropriate backup and recovery arrangements, but do not treat a backup as permission for unsafe techniques. The rules of engagement remain the primary control.

Define critical escalation and stop conditions

Agree what requires immediate contact rather than waiting for the final report, such as confirmed access to highly sensitive data, an active compromise, unexpected instability or contact with an unauthorised third party. Name primary and backup contacts and who can pause testing. Unless incident response has been separately agreed, the provider’s role is limited to reporting and agreed escalation; the customer’s incident-management process remains responsible for containment, investigation and notification decisions.

Control late discoveries and scope changes

If testing reveals an unlisted host, API, identity route or supplier dependency, pause activity against it, confirm ownership and authority, assess operational risk and record whether it is added, deferred or excluded. Association with an in-scope domain does not automatically grant permission to test a newly discovered asset.

Describe the approach and depth

Explain how automated coverage and human investigation will be combined, which recognised methodologies inform the work and how business logic, access control and chained weaknesses will be examined. Name any assumptions about accounts, architecture information or test data. Methodology should support repeatability and safety while leaving room for expert judgement.

Specify evidence and deliverables

Define what the customer will receive: live notification of material findings, reproducible technical evidence, severity rationale, practical remediation guidance, an executive view, a technical report and any portal access. Require limitations and untested areas to be stated clearly so the final report cannot be mistaken for assurance over a wider environment.

Include remediation support and retesting

The proposal should explain how questions will be handled after delivery, which fixes are eligible for retest, the retest window and what closure evidence will be provided. A report identifies work; retesting checks whether the agreed fixes address the previously demonstrated finding within the agreed retest scope and records any remaining limitations.

Hold a final go or no-go review

Confirm that written authorisation is complete, scope and rules use the same version, accounts and access routes work, monitoring and escalation contacts are available, required supplier approvals exist and no recent change or incident makes the window unsafe. If a critical prerequisite is missing, explicitly delay, reduce or revise the scope rather than allowing an unrecorded compromise to become the test plan.

Understand the limits

A penetration test is a time-bounded assessment of an agreed scope. It cannot prove that no vulnerability exists, that an incomplete inventory is complete or that a service will remain secure after it changes. Combine testing with secure design, asset management, monitoring, vulnerability management and proportionate retesting.

Ready for the Pentesys point of view?

This guide covers the essentials. Continue into our technical analysis for a firmer position, practical implications and recommended action.

Read “A testing methodology should protect rigour without constraining curiosity” →
TALK TO PENTESYS

Apply this guidance to your environment.

Tell us what you need to understand, test or prove. We'll help you choose a proportionate next step—without forcing the conversation into a predefined package.

Discuss your penetration-testing scope →Explore Validate

Keep reading

Pentesys trust and assurance

Recognised credentials. Responsible AI. Experienced people.

Clear evidence of our company standards, testing services and access to AI programmes.

Independent company assurance

CREST member company for Penetration Testing in EMEA

CREST member company

Penetration Testing in EMEA. Company standards independently assessed by CREST.

Valid until 1 November 2026View company certificate
CREST Security Testing accreditation for penetration testing

CREST-accredited human-led penetration testing

Independent assurance for Pentesys’s human-led penetration-testing service.

Human-led testingView CREST listing

AI-enabled testing assurance

CREST accreditation for AI-enabled penetration testing

CREST-accredited AI-enabled penetration testing

Pentesys is one of the first ten companies worldwide accredited by CREST for AI-enabled penetration testing. The accreditation assesses the responsible, secure and appropriate use of AI in penetration-testing services.

AI-enabled penetration testingView CREST announcement

Responsible-AI commitment

CREST AI Charter signatory

CREST AI Charter signatory

A separate commitment to responsible, transparent and accountable use of AI in cybersecurity.

Responsible-AI commitmentAbout the CREST AI Charter

Secure organisational baseline

Cyber Essentials certified

Cyber Essentials certified

Pentesys is certified across the whole organisation against the Cyber Essentials baseline controls.

Recertification due 12 August 2027View Cyber Essentials certificate

Controlled AI programme access

Pentesys participates in Anthropic’s Cyber Verification Program (CVP) for Claude and has approved access to OpenAI Daybreak Blue.

Anthropic CVP for Claude

Participation in Anthropic’s Cyber Verification Program.

Programme participationAbout Anthropic CVP

OpenAI Daybreak Blue

Approved access for defensive cybersecurity work.

Approved programme accessAbout Daybreak Blue

CREST accreditation applies to Pentesys’s service delivery, not to an AI model, the Portal or an appliance.

Meet the expertise behind our testing