ESSENTIAL GUIDANCE · BUYER GUIDE · 4 min read

Part of Validate insights →

Internal Network Penetration Testing: Scope and Access

Plan internal network penetration testing around starting access, identities, segmentation, operational constraints, useful evidence and fixes.

Technical review lead: James Hinton · Offensive security lead

Plan internal network penetration testing around starting access, identities, segmentation, operational constraints, useful evidence and fixes.

Need an acronym translated?Open the cyber glossary →

What should an internal network penetration test establish?

An internal test asks what an attacker could reach from one agreed point inside the network. That point might be a normal user account, a managed test device, or another approved foothold.

Start with the business question. Can access to one area expose a critical service, cross a boundary, or reach data the starting identity should not control? The answer depends on the scope and access you provide. An internal test does not cover every device or identity by default.

Agree the starting position before comparing quotes

Record whether the tester begins with a standard account, a managed endpoint, a network connection, or limited knowledge. State which site, VPN, or remote access route is involved.

These assumptions greatly change what can be checked in the time available. External testing starts from an agreed internet-facing point; internal testing uses a different boundary. A combined engagement can cover both when each part is clearly approved and priced.

Map identities, segments and key dependencies

Supply a current network overview, address ranges, sites and service owners. Identify directory and identity services, privileged administration, key servers, remote access routes and cloud connections.

Describe the boundaries that should stop movement between users, teams or services. Confirm whether wireless, operational technology (OT), third-party systems and cloud identity work are included or scoped separately. Owning a network range does not mean you may test every connected supplier system.

Internal penetration testing checklist: access and coordination

  • Agree representative accounts, approved connection methods and safe test data.
  • Name the system owner, technical contacts and escalation route.
  • Set testing windows, allowed techniques, exclusions and stop conditions.
  • Coordinate monitoring, allow-listing and incident response contacts where needed.
  • Identify fragile systems and business-critical work before testing starts.
  • Confirm explicit written authorisation from the responsible system owners.

Use the prep meeting to clear up any uncertainty. Missing access or a wrong inventory can use the whole test window without answering the main question.

Choose the method around the question

Vulnerability scanning can provide broad, repeatable coverage. AI-enabled testing can investigate suitable, authorised scopes with expert oversight and evidence validation. Human-led work adds deeper investigation for complex identities, business logic and attack paths where agreed.

Choose the route that fits the environment and the internal penetration test scope you need. A customer-hosted AI appliance is only a deployment model. It does not replace a defined assessment scope or prove that every internal control was tested.

Specify evidence, limits and follow-through

Ask for a clear scope record, starting assumptions, tested boundaries, confirmed findings, impact explanation and practical steps to fix the issue. Record limits and areas that could not be checked.

Technical teams need enough context to reproduce and fix the issue safely. Leadership needs to understand which business decision the evidence supports. Agree critical-finding escalation, a debrief and the retest scope and timing in the quote.

What affects the cost of internal testing?

Effort depends on the mix of services and identities, number of segments or sites, starting access, required depth and operational constraints. Repeated standard builds may be different from many unique systems.

Travel, restricted windows, extra environments or separately scoped investigation can affect the quote. Compare these assumptions with the price rather than relying only on an IP count or an unclear day rate.

Prepare for remediation before the report arrives

Assign an owner who can coordinate fixes and keep evidence. Distinguish containment, a permanent corrective action and a documented risk decision.

A customer-reported fix is not the same as independent retest evidence. Agree on which material changes will undergo retesting and define what closure means for each finding. Testing provides evidence within an agreed scope at a point in time; major changes may need a new or updated scope.

Q&A

Common questions

Does internal testing include Active Directory?

Only if the agreed scope includes the relevant directory services, identities, and activities. Confirm the starting access and depth rather than assuming they follow from the word internal.

Is an internal test the same as a vulnerability scan?

No. A scan finds likely weaknesses; a penetration test checks approved attack paths and their impact. The agreed method and evidence requirements should make that difference clear.

Can the work run remotely?

Sometimes, with an agreed and approved access arrangement. Network design, operational constraints and the assurance goal decide whether remote, on-site or combined delivery fits.

Does an on-premise AI pilot cover our whole internal estate?

No. Pilot approval, deployment boundaries and each authorised testing scope must be agreed separately.

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 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 1st November 2027View 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