Skip to content
Sovereign SecureSovereign Secure

Penetration Testing

Internal Penetration Testing

We start where a real attacker would be after one successful phish, inside your network, and show how far they could get: through Active Directory, across your servers and into sensitive data. Reports come from a PCI QSA company and stand as evidence for PCI DSS, ISO 27001 and customer due diligence.

Prefer to talk? Call +44 161 523 5276

  • Assumed breach, from a standard user
  • Active Directory attack paths to domain admin
  • Mapped to PCI DSS 11.4.2 and 11.4.5

The short answer

Internal penetration testing is an authorised, manual attack launched from inside your network, the way a phished employee, rogue insider or malware would operate. Testers try to escalate from an ordinary user account to domain admin through Active Directory, move laterally and reach sensitive data. PCI DSS Requirement 11.4.2 requires one at least every 12 months.

On this page
  1. What is an internal penetration test?
  2. What does internal network penetration testing cover?
  3. How is an internal penetration test carried out?
  4. How do attackers reach domain admin from inside the network?
  5. How do you test lateral movement?
  6. Does internal penetration testing include segmentation testing?
  7. How does remote internal penetration testing work?
  8. How much does an internal penetration test cost?
  9. What do you receive after the test?
  10. Do you also need an external penetration test?
  11. Which compliance requirements does an internal penetration test meet?
  12. Why choose Sovereign Secure for internal penetration testing services?
  13. Get a fixed quote for your internal penetration test

Internal penetration testing is a manual, authorised attack on your network from the inside that shows what someone already there could do: an employee whose laptop has been phished, a contractor on a meeting-room port, or malware on one workstation. Our testers start from that foothold, usually a standard domain user account, and try to reach domain admin, critical servers and sensitive data. We report every path we prove, with evidence and the fix that breaks it.

It is the inside half of our network and infrastructure penetration testing service. For the view from the internet, pair it with external penetration testing.

What is an internal penetration test?

An internal penetration test is a time-boxed, authorised attack on your internal systems by a qualified tester working from inside the network. Internal network penetration testing, internal infrastructure penetration testing and an “internal pentest” are the same service under different names.

Most tests assume the breach has already happened, so no time goes on phishing. You choose the starting points that match your risks:

Scenario Starting access Question it answers
Assumed breach A standard domain user on a normal laptop build What can a phished employee reach?
Unauthenticated access A live network port or guest Wi-Fi What can a visitor who plugs in achieve?
Privileged insider A real role, such as helpdesk or developer Can staff exceed what their role allows?
Third-party access A supplier’s VPN or remote support account Does the supplier reach only what it should?

What does internal network penetration testing cover?

Everything reachable from the starting point, within the scope you authorise:

Area What we test Weaknesses we look for
Active Directory Users, groups, permissions, Group Policy, trusts, Certificate Services Kerberoastable accounts, vulnerable certificate templates, excessive rights
Authentication traffic LLMNR, NBT-NS, NTLM, SMB signing Credential capture and relay
Servers and workstations Windows and Linux hosts, patching, local administrator accounts Missing patches, shared local admin passwords, unsupported systems
File shares and databases SMB and NFS shares, SQL servers, intranets Passwords in scripts, open shares holding personal data
Management interfaces Hypervisors, backup servers, iLO and iDRAC, switches Default credentials, consoles reachable from user networks

Server internal penetration testing, where only critical servers are in scope, uses the same method with a narrower target list.

How is an internal penetration test carried out?

An internal pen test moves from paperwork to proof in five steps:

  1. Scoping and authorisation. We agree the networks, sites, domains and starting scenarios, the rules of engagement and the testing window, and you sign written authorisation.
  2. Access set-up. You import our test virtual machine, connect a test device or issue VPN access, plus a standard domain user account if the scenario starts from one.
  3. Discovery. From that starting point we map live hosts, services, file shares and the Active Directory domain.
  4. Exploitation and lateral movement. We capture and reuse credentials, follow Active Directory attack paths and move between systems towards the agreed targets, logging every action with a timestamp.
  5. Reporting. The report and a debrief with your team, followed by the retest described below.

Every test follows the five stages of penetration testing: planning and reconnaissance, scanning, gaining access, maintaining access, and analysis and reporting.

How do attackers reach domain admin from inside the network?

Usually by chaining medium-risk misconfigurations, not one dramatic exploit, which is why an Active Directory security assessment needs a human tester. A typical chain:

  1. Capture a credential by poisoning LLMNR or NBT-NS lookups, or relaying NTLM authentication to hosts without SMB signing.
  2. Map the domain. Any domain user can read most of Active Directory; graphing groups, sessions and permissions shows the shortest route to Domain Admins.
  3. Crack service accounts. Kerberoasting and AS-REP roasting expose hashes for weak passwords, cracked offline without touching the account.
  4. Abuse Certificate Services. A misconfigured AD CS template (such as ESC1) can let a normal user obtain a certificate as an administrator.
  5. Abuse rights and delegation. GenericAll or WriteDACL rights, or unconstrained delegation, let one account take over another, up to replicating every password hash from a domain controller (DCSync).

The report shows where each chain can be broken, so you can fix the cheapest link first. Our guide to Active Directory penetration testing covers each technique in depth. If your domain synchronises to Microsoft Entra ID, the same chain can continue into the cloud, which Azure and Entra ID penetration testing covers.

How do you test lateral movement?

Lateral movement is how an attacker spreads between machines using stolen credentials and normal admin protocols such as SMB, WinRM and RDP. We test whether harvested credentials work elsewhere and whether privileged accounts leave reusable credentials on ordinary machines. We log when each action happened, so your security team can check which steps raised an alert and which went unseen. Lateral movement is also how ransomware reaches every server at once; our guide on how to prevent ransomware sets out the controls that stop it spreading.

Does internal penetration testing include segmentation testing?

It can, and if segmentation reduces your PCI DSS scope it must. Requirement 11.4.5 requires segmentation controls to be tested at least every 12 months and after any change to them; 11.4.6 makes it every six months for service providers. From each out-of-scope network we scan towards the cardholder data environment (CDE) and check every open path against your approved flows. Our PCI DSS penetration testing service covers the internal, external and segmentation tests in Requirement 11.4.

How does remote internal penetration testing work?

Remote internal penetration testing gives our testers a foothold inside your network without a site visit, through a test virtual machine, a small test device or your own VPN, and most of our internal tests run this way. The right option depends on your estate:

Option How it works Best for
Test virtual machine You import our VM; it connects out to us over an encrypted tunnel Virtualised and data-centre estates
Test device You plug our pre-configured device into a network port, then return it Offices, branches and stores
Your VPN or VDI You issue an account, as for a remote worker What a compromised remote user can reach
On-site A tester attends in person Isolated networks, wireless penetration testing in scope

How much does an internal penetration test cost?

It depends mainly on how many sites, network segments and Active Directory domains are in scope. Published prices from UK providers we reviewed in September 2026 include internal network tests from £1,800, and UK pricing guides we reviewed put typical day rates at about £1,000 to £1,500 per tester-day. We quote a fixed price once scope is agreed.

Cost driver Why it changes the effort
Sites and network segments Each is another starting point or segmentation path
Active Directory size and trusts More domains and trusts mean more attack paths to map
Segmentation testing A scan from every out-of-scope network, twice a year for service providers

Our penetration testing cost guide compares prices across test types.

What do you receive after the test?

  • A plain-English executive summary for leadership, auditors and customers
  • Attack-path narratives showing where each chain breaks
  • Findings with evidence, CVSS ratings and remediation steps
  • An Active Directory appendix: privileged group members, Kerberoastable accounts, risky delegation
  • A timeline of tester actions for your detection team
  • A debrief call, then a retest of remediated findings, with terms confirmed in your fixed-price proposal

A single finding looks like this (illustrative, not client data):

Field Example
Finding Service account with a weak password, exposed to Kerberoasting
Severity High
Impact The account is local administrator on every file server
Remediation Use a group managed service account, remove unneeded admin rights, alert on RC4 ticket requests

Do you also need an external penetration test?

Usually, yes: an internal test shows what an attacker could do once inside, while an external penetration test shows whether they could get in from the internet, and PCI DSS requires both (11.4.2 and 11.4.3). Our comparison of internal vs external penetration testing explains which to prioritise if you can fund only one.

Internal and external describe where a test starts. The “three types of penetration testing” people often quote, black box, grey box and white box, describe how much the tester is told in advance instead, and an assumed breach internal test is usually grey box. Our overview of the types of penetration testing covers both ways of classifying a test.

Which compliance requirements does an internal penetration test meet?

Framework Requirement How an internal test helps
PCI DSS v4.0.1 11.4.2: internal test every 12 months and after significant change Direct evidence against your methodology
PCI DSS v4.0.1 11.4.5 and 11.4.6: segmentation testing Proof out-of-scope networks cannot reach the CDE
ISO/IEC 27001:2022 Annex A 8.8 (technical vulnerabilities), 8.22 (segregation of networks) Independent evidence the controls work
Cyber Essentials Plus Authenticated vulnerability scan of sampled devices Finds wider issues before the audit; does not replace it

The NCSC’s penetration testing guidance treats a test as a check on your vulnerability management, so each finding names the process gap behind it. PCI requirement text is in the PCI SSC document library. Preparing for Cyber Essentials Plus? Test a few weeks before the audit.

Why choose Sovereign Secure for internal penetration testing services?

  • A PCI QSA company. The PCI Security Standards Council approves us as a Qualified Security Assessor company, Qualified PIN Assessor and Card Production Security Assessor, and we sit on its Global Executive Assessor Roundtable for 2026 to 2028. We know what assessors expect as 11.4.2 and 11.4.5 evidence.
  • An IASME Cyber Essentials certification body, issuing CE and CE+ certificates.
  • ISO 27001 certified, so the information security management system that governs your credentials and findings is independently audited.
  • Clients in payments, banking, retail and hospitality, including Fiserv, Accor, JCPenney, Cashplus and Ahli United Bank.
  • UK headquarters in Accrington, Lancashire. Remote testing by default, on-site when the scope needs it.

Get a fixed quote for your internal penetration test

Tell us your sites and network segments, rough user and server numbers, your Active Directory domains, whether remote testing suits you, and why you need the test (PCI DSS, ISO 27001, insurance or a customer). We will confirm scope and send a fixed-price proposal. Use the penetration testing quote form or call +44 161 523 5276.

Last reviewed October 2026 by the Sovereign Secure assessment team.

Trusted by banks, payment providers and global brands

  • Accor
  • Fiserv
  • JCPenney
  • Ticketmaster
  • Nitecrest
  • Cashplus
  • Ahli United Bank
  • Kuwait Finance House
  • AYA Bank
  • Bank of Palestine
  • Liquid Pay
  • DataFlow Group
  • Wilmington
  • The Growth Company
  • Wahyukart

FAQ

Frequently asked questions

Can't find your answer? Call us on +44 161 523 5276 or send us a message.

What is internal penetration testing?

Internal penetration testing is a manual, authorised attack carried out from inside your network, usually starting from a standard user account or a live network port. It shows how far an insider or an attacker with a foothold could get, for example to domain admin or sensitive data, and what would stop them.

Do you need to be on-site for an internal pen test?

Usually not. Most internal tests run remotely through a test virtual machine or a small test device on your network that connects out to us over an encrypted tunnel. We attend on-site when isolated networks, wireless or physical access make that the better option.

Will an internal penetration test disrupt our network?

It should not. We agree rules of engagement first, avoid denial-of-service techniques, keep password attacks below your lockout thresholds, remove any accounts or files we create, and call your named contact straight away if a system looks unstable or we find a critical issue.

What access do you need for an internal penetration test?

Typically a standard domain user account with the same rights as a new starter, somewhere to run our test machine, and the IP ranges in scope. For segmentation testing we also need a connection point in each out-of-scope network and your documented list of approved flows into the cardholder data environment.

How often should we run an internal penetration test?

At least once a year, and after significant change such as a new domain, a data-centre or cloud migration, a merger or a network redesign. That matches PCI DSS Requirement 11.4.2. If you rely on segmentation to reduce PCI scope, 11.4.5 adds segmentation tests every 12 months, or every six months for service providers.

Is an internal vulnerability scan the same as an internal pen test?

No. A vulnerability scan is automated and lists missing patches and known weaknesses, and PCI DSS asks for one every three months under 11.3.1. An internal penetration test is manual: it chains weaknesses together and proves what they lead to, such as full domain compromise.

How long does an internal penetration test take?

Most single-site tests with one Active Directory domain take a few days of testing, with the report following. Each extra site, domain, trust or segmentation path adds days, and we confirm the timeline during scoping.

Should we tell our IT or security operations team about the test?

That is your choice. Telling only a small group lets you see whether your monitoring and endpoint detection spot us, and we give you a timeline of our actions afterwards so you can check. For a covert, goal-based exercise across people, process and technology, see our red team assessments.

Free consultation

Talk to an assessor

We aim to reply within one working day, and send a fixed quote once your scope is confirmed.

  • PCI SSC-approved QSA, QPA, CPSA, P2PE and 3DS assessors
  • IASME-licensed Cyber Essentials certification body
  • Clients across the UK, US, Europe, Middle East and Asia since 2012

“The Cyber Security Services were delivered on time and price was competitive.”

Beverley McGowan, Director, Specialists Hub. Read the full testimonial

By sending this form you agree to us contacting you about your enquiry. See our privacy policy.

We aim to reply within one working day. The first consultation is free.