main logo icon

Published on

August 18, 2026

|

23 min read

Network Penetration Testing: What It Is, Types, Process and Cost (2026)

A guide to network penetration testing in 2026: what it is, the six test types and how they fit together, how it differs from a vulnerability scan and a red team, the phases, common findings, delivery, scoping, cost drivers, deliverables and PCI DSS 11.4.

Arafat Afzalzada

Arafat Afzalzada

Founder

Network Security

Summarize with AI

ChatGPTPerplexityGeminiGrokClaude

TL;DR

Network penetration testing is an authorized, time-boxed attack on an organization's network, run by penetration testers to prove how far an intruder could get. It covers up to six test types: external, internal, Active Directory, segmentation, wireless and cloud-connected networks. It differs from a vulnerability scan because weaknesses are exploited and chained into attack paths, and from a red team engagement because it aims for coverage of the scope rather than a covert test of detection and response. NIST SP 800-115 describes four phases: planning, discovery, attack and reporting. In Stingrai's 2026 data, internal network tests returned a median of 11 verified findings with 92% High or Critical, and outdated or unpatched software was 56.9% of them. PCI DSS v4.0.1 Requirement 11.4 asks for internal and external penetration testing at least once every 12 months and after any significant change, with segmentation testing where segmentation isolates the cardholder data environment. Cost follows testing days, which follow live hosts, sites, Active Directory size and start positions. Stingrai scopes network work per engagement, human-led, with the retest included.

Network penetration testing is an authorized, time-boxed attack on an organization's network, carried out by penetration testers to prove how far a real intruder could get and what would stop them. NIST SP 800-115 defines penetration testing as "security testing in which assessors mimic real-world attacks to identify methods for circumventing the security features of an application, system, or network." A network penetration test (also written network pen testing or network pentest) applies that to infrastructure: the internet-facing perimeter, the internal network of servers, workstations and devices, Active Directory, the segmentation between zones, Wi-Fi, and the links from the network into the cloud.

The demand for it follows how intrusions start. Exploitation of vulnerabilities is the most common initial access vector in Verizon's 2026 Data Breach Investigations Report, at 31% of breaches with a known vector, and exploits started 32% of the intrusions Mandiant investigated in 2025, the leading vector for the sixth consecutive year. CISA's Known Exploited Vulnerabilities catalog held 1,779 entries at its 10 November 2026 release, 295 of them added in 2026, already more than the 245 added in all of 2025.

Quick answer: A network penetration test combines up to six test types: external, internal, Active Directory, segmentation, wireless and cloud-connected networks. Testers plan the work with you, discover what is reachable, attack it under agreed rules, and report proven attack paths with fixes, then retest. It differs from a vulnerability scan because weaknesses are exploited and chained, and from a red team engagement because it aims for coverage rather than stealth. PCI DSS v4.0.1 requires internal and external penetration testing at least once every 12 months and after any significant change. This guide covers each part at briefing level and links to the detailed page for every sub-topic.

Network penetration testing at a glance

Question

Short answer

What is it?

An authorized, simulated attack on network infrastructure that proves which weaknesses can be exploited and how they chain into attack paths

What are the types?

External, internal, Active Directory, segmentation, wireless and cloud-connected networks

How is it different from a vulnerability scan?

A scan lists possible weaknesses. A penetration test exploits them to confirm they are real and shows how far they lead

How is it different from a red team engagement?

A penetration test covers a defined scope as fully as time allows. A red team engagement pursues objectives covertly to test detection and response

What are the phases?

Planning, discovery, attack and reporting, in NIST SP 800-115's four-phase model

How is it delivered?

External testing remotely from the internet. Internal testing on-site, through a VPN, or through a testing device placed on the network

How long does testing take?

Stingrai's published typical figures are 1 to 5 testing days for external and 1 to 10 testing days for internal, set by scope

How often?

PCI DSS v4.0.1: at least once every 12 months and after any significant change. NYDFS: at least annually

What do you receive?

Findings with evidence, an attack path narrative, an executive summary, remediation guidance and a retest

What is network penetration testing?

A network penetration test answers one question with evidence: starting from a position an attacker could realistically hold, what can be reached, taken over and done? The PCI Security Standards Council's definition in PCI DSS v4.0.1 is the clearest short version: "Penetration tests simulate a real-world attack situation intending to identify how far an attacker could penetrate an environment, given differing amounts of information provided to the tester."

Three things separate it from other security checks:

  • It is authorized and bounded. Scope, dates, permitted techniques and contacts are agreed in writing before testing starts. The discussion of NIST SP 800-53 control CA-8 says: "All parties agree to the rules of engagement before commencing penetration testing scenarios."

  • Weaknesses are exploited, under control, to prove impact. A finding is a demonstrated result with evidence, such as access to a server or control of an account, and the test shows how several findings chain together.

  • It is human work. PCI DSS v4.0.1 calls penetration testing "a highly manual process" in which "the tester uses their knowledge of systems to gain access into an environment."

Network testing is the infrastructure half of penetration testing. The PCI SSC's Penetration Testing Guidance (September 2017) defines network-layer testing as "Testing that typically includes external/internal testing of networks (LANS/VLANS), between interconnected systems, and wireless networks." Application-layer testing of websites, web applications and APIs is the other half, and it is scoped separately.

Types of network penetration testing

"Network penetration testing" is a family of six tests. Each starts from a different position and answers a different question, so a quote that covers one does not cover the others.

Test type

Where the tester starts

The question it answers

Detailed guide

External network

The public internet, with no credentials

What can an outsider reach and exploit on the perimeter?

External penetration testing

Internal network

Inside the network, usually as an ordinary user or a device on a user network

How far does an intruder get after the perimeter fails?

Internal penetration testing

Active Directory

An ordinary domain account

How many routes lead from a standard user to control of the directory?

Active Directory security assessment

Segmentation

A network that is meant to be out of scope

Can networks outside a protected zone reach into it?

PCI DSS penetration testing

Wireless

Within radio range of a site

Is Wi-Fi a route onto the wired network?

WiFi penetration testing

Cloud-connected networks

The identity and network links between the corporate network and the cloud tenant

Can a foothold on the network become control of cloud resources?

Cloud penetration testing

Diagram of where each of the six network penetration test types starts

External network penetration testing

An external test starts where an outside attacker starts: on the internet, with no credentials and only public information. PCI DSS v4.0.1 defines it as "testing the exposed external perimeter of trusted networks, and critical systems connected to or accessible to public network infrastructures." In practice that means VPN gateways, firewalls and other edge appliances, remote access portals, mail and DNS, exposed management interfaces, and hosts nobody remembers owning. Login surfaces are checked for weak and reused passwords and missing multi-factor authentication, which is where password spraying exposure shows up. The full scope, method and findings are in the external penetration testing guide.

Internal network penetration testing

An internal test assumes the perimeter has already failed. NIST SP 800-115 describes it this way: "assessors work from the internal network and assume the identity of a trusted insider or an attacker who has penetrated the perimeter defenses." The tester usually begins from an assumed-breach position, such as a standard domain account or a device on a user network, and works toward higher privileges and sensitive systems. The test measures discovery of hosts and services, credential exposure, vulnerable internal services, privilege escalation and lateral movement between hosts and network segments. Depth on scope, start positions, delivery and what drives effort is in the internal penetration testing guide, and the two are compared side by side in internal vs external penetration testing.

Active Directory testing

Where the internal network is run through Active Directory, the internal test includes it, because that is where privilege is decided. A dedicated Active Directory assessment goes further: from an ordinary domain account it maps and proves the routes to control of the directory through Kerberos weaknesses such as Kerberoasting, delegation, access control lists, Group Policy, certificate services and domain trusts. An internal network test reports exploited hosts, missing patches and segmentation results. An Active Directory assessment reports attack paths through identities and permissions, and which single fixes remove the most paths. StingAD: from one low-privilege account to Domain Admin shows what that looks like, and the Active Directory penetration testing guide covers scope and cost.

Segmentation testing

Segmentation testing checks a claim: that a sensitive zone cannot be reached from the networks around it. The tester sits in a network that is supposed to be out of scope and tries to reach the protected zone. PCI DSS v4.0.1 Requirement 11.4.5 requires this where segmentation isolates the cardholder data environment (CDE), and one element of the requirement reads: "Confirming that the segmentation controls/methods are operational and effective, and isolate the CDE from all out-of-scope systems." The standard's guidance explains why: "Many attacks have involved the attacker moving laterally from what an entity deemed an isolated network into the CDE." The same test applies to any isolated zone, such as backup infrastructure, operational technology or a production environment. A segmentation test can end with good news. One of the 1,206 verified records in Stingrai's State of Penetration Testing 2026 is not a vulnerability: it documents network segmentation verified effective.

Wireless testing

A wireless test asks whether the radio network is a way onto the wired one. It covers the authentication behind each SSID, separation of guest and corporate Wi-Fi, rogue access points, and how laptops and phones behave when a look-alike network appears, the evil twin problem. It needs a tester or a testing device within radio range of each site. PCI DSS v4.0.1 Requirement 11.2.1 separately sets a detection duty: "The presence of wireless (Wi-Fi) access points is tested for", and "Testing, detection, and identification occurs at least once every three months." Scope and method are in the WiFi penetration testing guide.

Cloud-connected networks

Few networks stop at the office wall. Directory synchronization, site-to-site VPNs and private links join the corporate network to AWS, Azure and Google Cloud, and an attack path can cross that join in either direction. In CISA's August 2026 advisory on two red team assessments, the team "achieved full domain compromise and accessed sensitive business systems (SBSs) and cloud resources" in both organizations, and one lesson reads: "Cloud environments are often an underestimated risk." A network test should state whether hybrid identity and cloud links are in scope. The providers allow customer testing under published rules: AWS permits tests of listed services "without prior approval", Google Cloud says "you are not required to contact us", and Microsoft publishes Security Testing Rules of Engagement for its online services. Control-plane depth belongs in a cloud penetration test, and identity scope is covered in how to scope Azure and Entra ID.

How the types fit together in one program

The six types follow the order of a real intrusion, so a network testing program is one plan, not six purchases:

  1. Outside in. External testing shows what an attacker can reach and exploit from the internet.

  2. Inside out. Internal testing starts from an assumed-breach position and shows what happens next, with Active Directory in scope.

  3. Across boundaries. Segmentation testing runs from the internal position against the zones that are supposed to be isolated.

  4. Over the air and into the cloud. Wireless testing covers each site, and cloud-connected scope covers hybrid identity and network links.

  5. Fix, retest, repeat. Findings are fixed and retested, and the cycle repeats at least annually and after significant change.

Your situation

Tests to include

The network has never been tested

External and internal, with Active Directory inside the internal scope

A cardholder data environment under PCI DSS

External and internal, plus segmentation testing wherever segmentation reduces scope

A Windows domain with many privileged accounts, trusts or certificate services

Add a dedicated Active Directory security assessment

Offices with corporate or guest Wi-Fi

Add a wireless assessment for each site, or a representative sample

Hybrid identity or private links into AWS, Azure or Google Cloud

Add cloud-connected scope, or a separate cloud penetration test

A tested, hardened network and a security operations team to exercise

Follow with a red team or purple team engagement

Network penetration testing vs vulnerability scanning

A vulnerability scan and a penetration test are different activities that support each other. NIST SP 800-115 draws the line in one sentence: "While vulnerability scanners check only for the possible existence of a vulnerability, the attack phase of a penetration test exploits the vulnerability to confirm its existence." The PCI SSC's Penetration Testing Guidance sets the two side by side:

Vulnerability scan

Network penetration test

Purpose

"Identify, rank, and report vulnerabilities that, if exploited, may result in an intentional or unintentional compromise of a system."

"Identify ways to exploit vulnerabilities to circumvent or defeat the security features of system components."

How

"Typically a variety of automated tools combined with manual verification of identified issues."

"A manual process that may include the use of vulnerability scanning or other automated tools, resulting in a comprehensive report."

Output

Potential risks from known vulnerabilities, ranked by CVSS score

Each verified vulnerability, how it was exploited and how far it led

PCI DSS v4.0.1 frequency

External scans by an Approved Scanning Vendor at least once every three months (11.3.2)

At least once every 12 months and after any significant change (11.4.2 and 11.4.3)

PCI DSS v4.0.1 is blunt about substituting one for the other: "Scanning for vulnerabilities alone is not a penetration test, nor is a penetration test adequate if the focus is solely on trying to exploit vulnerabilities found in a vulnerability scan." The discussion of NIST SP 800-53 control CA-8 says the same: penetration testing "goes beyond automated vulnerability scanning and is conducted by agents and teams with demonstrable skills and experience."

A network needs both. Scanning gives breadth and frequency across every host. Penetration testing shows which of those weaknesses an attacker can actually use, and finds the ones a scanner has no signature for: a reused administrator password, an over-permissive delegation, a firewall rule that lets a guest network reach a database. The full comparison is in vulnerability assessment vs penetration testing.

Network penetration testing vs red teaming

A red team engagement uses many of the same techniques for a different purpose. NIST SP 800-53 describes the relationship in the discussion of CA-8(2), its red team enhancement: "Red team exercises extend the objectives of penetration testing by examining the security and privacy posture of organizations and the capability to implement effective cyber defenses."

Network penetration test

Red team engagement

Goal

Find and prove as many exploitable weaknesses and attack paths in scope as time allows

Reach agreed objectives and measure whether defenders detect and respond

Defenders

Usually informed, so testing can be open and thorough

Usually uninformed, apart from a small trusted group

Scope

Named ranges, domains, sites and start positions

The organization, including people and sometimes premises

Duration

Days to weeks

Weeks to months

Output

Findings with evidence, attack path narrative, retest

A narrative of the operation, detection gaps and lessons for the security operations team

CISA's published red team assessments show the difference in practice. Its July 2024 advisory describes "a no-notice, long-term simulation of nation-state cyber operations" against a federal agency, and its November 2024 advisory covers an assessment of a critical infrastructure organization conducted "over approximately a three-month period." Neither was trying to list every weakness. Both were measuring whether the organization would notice.

For most organizations the order matters: test and fix the network first, then test the defenders. Choosing between the engagement types is covered in purple team vs red team vs penetration test, and what red teaming is covers how an engagement runs.

How a network penetration test works: the four phases

NIST SP 800-115 divides a penetration test into four phases and adds: "There are many acceptable ways of grouping the actions involved in performing penetration testing." Providers name the steps differently, but the work is the same.

Phase

What happens

What you see

1. Planning

In NIST's words, "rules are identified, management approval is finalized and documented, and testing goals are set." No testing occurs

Scope, rules of engagement, written authorization, contacts and testing windows

2. Discovery

Testers map live hosts, open ports and services, gather names and addresses, and analyze what they find for weaknesses

Scan traffic from the agreed source addresses, and questions about anything unexpected

3. Attack

Testers attempt to exploit the weaknesses found, escalate privileges and move to other systems. Each success feeds new discovery, the loop in NIST's model

Findings as they are confirmed, and immediate notice of anything critical

4. Reporting

NIST notes that reporting "occurs simultaneously with the other three phases" and ends with a report that describes the vulnerabilities, rates the risk and gives guidance

The report, a walkthrough, then the retest

Three points matter to a buyer at this level:

  • The methodology should be written down. PCI DSS v4.0.1 Requirement 11.4.1 requires a penetration testing methodology that is "defined, documented, and implemented", and the PCI SSC's guidance lists OSSTMM, NIST SP 800-115, the OWASP Testing Guide and the Penetration Testing Execution Standard among industry-accepted methodologies. Our penetration testing methodology guide compares them phase by phase.

  • Attack paths should be described in a shared vocabulary. MITRE ATT&CK, at version 20 since its 13 October 2026 release, lists 15 Enterprise tactics. Lateral Movement, one of them, "consists of techniques that adversaries use to enter and control remote systems on a network." A report that maps each step to ATT&CK lets your detection team check what it would have seen.

  • Exploitation is controlled. NIST is plain that the risk "can never be fully eliminated" and that testing should happen "only after careful consideration, notification, and planning." Rules of engagement set what is off limits, when testing runs, and when the tester stops and calls you.

What network penetration tests most often find

Stingrai's State of Penetration Testing 2026 analyzed 1,206 verified findings from 55 penetration tests run between October 2024 and August 2026. The network tests in that dataset split sharply by starting position:

Test type

Verified findings

Tests with findings

Median per test

High or Critical

Internal network

408

8

11

92%

External network

23

6

1

48%

Stingrai 2026 data: internal and external network penetration test findings

External tests returned a median of one finding per test. Inside the network the median was 11, and 92% of findings were High or Critical. Outdated or unpatched software was 56.9% of internal network findings, followed by misconfiguration and hardening (11.8%), injection (10.5%) and authentication and session weaknesses (8.6%). The sample is small, eight internal and six external tests with findings, so read it as one firm's evidence, not a market benchmark.

Public sources describe the same families of weakness:

  • Unpatched and end-of-life systems. Verizon's 2026 DBIR found that only 26% of the vulnerabilities in CISA's KEV catalog were fully remediated by organizations in 2025, down from 38%, and that the median time to full resolution rose to 43 days from 32.

  • Edge devices and remote access. Mandiant's M-Trends 2026 reports espionage groups deliberately targeting "edge and core network devices, such as virtual private networks (VPNs) and routers, that typically lack standard endpoint detection and response (EDR) telemetry." By Stingrai's count of CISA's KEV feed, 109 of the 540 entries added between 1 January 2025 and 10 November 2026 name an edge or remote access product: firewalls and VPN gateways, routers and SD-WAN, application delivery controllers, and remote support tools. The counting rule is in the external penetration testing guide.

  • Weak, shared and exposed credentials. In the red team assessment CISA published in November 2024, the team found credential material on a misconfigured Network File System (NFS) share, and in the assessment it published in July 2024, conducted in 2023, "unsecured administrator credentials" let the team "pivot freely throughout the Windows environment, which resulted in full domain compromise and access to tier zero assets." Microsoft's Windows LAPS documentation names the classic case: "Local administrator accounts often share the same password across many devices, which bad actors can exploit to move laterally across your environment."

  • Legacy protocols and relay weaknesses. Microsoft describes SMB signing as protection "from relay and spoofing attacks." Windows 11 version 24H2 Enterprise, Pro and Education require it in both directions and Windows Server 2025 requires it outbound only, so the setting has to be checked on each class of system.

  • Active Directory misconfiguration. M-Trends 2026 reports attackers "exploiting misconfigured Active Directory Certificate Services templates to create admin accounts that bypass password rotation." Kerberoastable service accounts, delegation and permissive access control lists belong to the same family.

  • Flat networks. CISA's July 2024 advisory gives the mitigation in one line: "Use robust network segmentation to impede lateral movement across the network."

  • Detection that watches hosts and misses the network. CISA's November 2024 advisory found the assessed organization "relied too heavily on host-based endpoint detection and response (EDR) solutions and did not implement sufficient network layer protections."

Each family has its own page: the top 10 network security vulnerabilities for dated examples and fixes, and the guides to Kerberoasting, password spraying and lateral movement for detection and defense.

How a network penetration test is delivered: on-site, shipped device or VPN

External testing needs no access at all: testers work from the internet, from source addresses they share with you so that your team can tell the test apart from a real attack. Internal and wireless testing need a position inside, and there are three ways to provide one. NIST SP 800-115 lists the options for technical work inside the network: access "either onsite, through an encrypted virtual private network (VPN) tunnel, or via a dedicated connection from a trusted environment."

Delivery

How it works

Suits

On-site

Testers work from your premises, connected to the networks in scope

Sensitive or isolated environments, wireless and physical checks in the same visit, several segments in one building

Shipped testing device

A pre-configured device, or a virtual machine image, is placed on the internal network and gives the testers a controlled, encrypted connection to work through

Multi-site organizations and remote-first teams, with no travel to schedule

VPN or jump host

You provide remote access into the network, usually to a dedicated host and with a test account

Environments that already have governed remote access for third parties

The delivery method changes logistics, not the methodology. What matters is where the starting position sits on the network, because a tester placed on a server network sees a different attack surface from one on a user network. Agree the placement, and how many start positions there are, at scoping. The internal penetration testing guide compares what each delivery position can and cannot see.

Stingrai delivers network engagements remotely or on-site where scoped. For Wi-Fi it ships a pre-configured Wi-Fi Pineapple device to each location, your team plugs it in, and the penetration testers run the assessment remotely, or the assessment is done on-site.

What to give the tester: scoping inputs

A quote is only as accurate as the scope behind it. These are the inputs that let a provider size a network test properly:

  • External: IP ranges, domains and cloud-hosted addresses you own, and who hosts each.

  • Internal: subnets and VLANs in scope with an estimate of live hosts, the number of sites and data centers, and any fragile or legacy systems.

  • Active Directory: domains, forests and trusts, approximate user and computer counts, and whether certificate services and hybrid identity are in use.

  • Segmentation: the protected zone, and the out-of-scope networks the claim must hold against.

  • Wireless: the SSIDs and sites to test.

  • Start positions: unauthenticated network access, a standard domain account, a managed laptop, or several of these.

  • Knowledge level: black box, grey box or white box. The PCI SSC's guidance notes that white-box and grey-box assessments "yield more accurate results and provide a more comprehensive test of the security posture of the environment than a pure black-box assessment." See black box vs grey box vs white box.

  • Rules of engagement: testing windows, techniques that are off limits, escalation contacts, and whether the security operations team is told. The PCI SSC's guidance suggests asking: "Are there any legacy systems that have known issues with automated scanning?"

  • Evidence needs: the frameworks the report must support, and who will read it.

A step-by-step version is in how to scope a penetration test.

What drives cost and duration

A network penetration test is priced on effort: the number of testing days the scope needs, multiplied by a day rate. Stingrai's network penetration testing page says a network penetration test typically costs US$5,000 to US$40,000 and above, and that PCI DSS engagements that bundle internal, external and segmentation testing commonly land at US$12,000 to US$25,000. That is a typical range across external and internal network testing, not a package price: Stingrai scopes network, Active Directory and wireless work per engagement, quotes a fixed price with the retest included and returns pricing within 24 hours of a quote request. The factors that set the number of days on the same page are the ones to expect from any provider:

Driver

Why it changes effort

Live hosts and IP ranges

The count of live internal and external addresses, not the size of the address space

Subnets, VLANs and sites

Each segment, site or data center adds discovery and pivoting time

Active Directory footprint

Domains, forests and trusts, and the depth of attack path testing

Start positions

External only, internal from an assumed-breach account, or both

Segmentation testing

Required for PCI DSS wherever segmentation reduces the cardholder data environment

Approach and delivery

Black, grey or white box, and remote or on-site testing

Duration. Stingrai's published typical figures are 1 to 5 testing days for external testing and 1 to 10 testing days for internal testing, with the schedule for each engagement fixed in writing at scoping. Calendar time is longer than testing time because authorization, access set-up, report review and the retest all take days of their own.

Rates. Published price data for network testing that a reader can check is scarce. One public source is the US government: GSA's CALC+ pricing tool lists what GSA describes as "fully burdened Not-to-Exceed Ceiling Rates awarded under GSA Multiple Award Schedule (MAS) contracts". On 13 November 2026 a search for "penetration tester" returned 442 awarded hourly rates from 143 contractors, from US$57.34 to US$320.56, with a median of US$156.29 as the tool displays it and a middle half of about US$126 to US$196. The spread reflects seniority as much as supplier: the lowest rate is for a level 1 labor category that asks for two years of experience, and the highest is for a level 5 category that asks for ten. These are labor-hour ceilings on government contracts, not project prices, and commercial quotes are structured differently. Our cost guide uses a wider search, every labor category whose title names penetration testing, and counted 553 rates from 163 contractors on 23 October 2026. On either cut, the range in hourly rates is one reason two quotes for the same network can sit far apart.

The practical rule is to compare quotes on testing days and what those days cover, not on the total. Our penetration testing cost guide explains day rates, how to compare penetration testing quotes works through an example, and the cost calculator gives a starting estimate.

Deliverables and retest

A network penetration test should leave you with evidence for three audiences:

Deliverable

What it contains

Who uses it

Findings

Each confirmed weakness with severity, affected hosts, reproduction evidence and remediation guidance

Infrastructure and security teams

Attack path narrative

How access moved from the starting position toward the objective, step by step

Security leads and detection teams

Executive summary

Plain-language risk, how far a tester got and what to fix first

Leadership

Scope and coverage statement

What was tested, from which start positions, with what method, and segmentation results where tested

Auditors and customers

Retest results

The status of every finding after fixes are deployed

Everyone

The PCI SSC's guidance says reports "should include a discussion of the steps, vectors, and exploited vulnerabilities that lead to penetration during testing for which remediation and retesting are required." The attack path narrative is that discussion, and it is what distinguishes a penetration test report from scan output.

Retesting closes the loop. PCI DSS v4.0.1 Requirement 11.4.4 requires that exploitable findings are corrected, and adds: "Penetration testing is repeated to verify the corrections." The retest window should match how long fixes really take: across the 163 findings with a tracked resolution time in Stingrai's 2026 data, covering all test types, the median was 26 days and the 90th percentile was 121 days.

Stingrai posts each finding to its PTaaS platform when it is confirmed, delivers an executive summary and a full technical report as a redactable PDF, includes retesting of fixed findings, and issues an attestation letter stating scope and testing dates with every human-led network engagement. To judge a report you have received, use how to evaluate a penetration test report, and see a sample penetration testing report for the format.

How often to test, and what the requirements say

The common baseline is once a year and after significant change. NIST SP 800-115 says that "penetration testing of an organization's network and systems on an annual basis may be sufficient", alongside "regularly scheduled network and vulnerability scanning." Where a rule applies, it sets the minimum.

PCI DSS v4.0.1 is the most specific. Requirement 11.4 is headed "External and internal penetration testing is regularly performed, and exploitable vulnerabilities and security weaknesses are corrected", and it sets out:

Requirement

What the standard says

Minimum frequency

11.4.1

"A penetration testing methodology is defined, documented, and implemented by the entity", with elements that include "Testing from both inside and outside the network" and "Network-layer penetration tests that encompass all components that support network functions as well as operating systems"

No interval stated: a standing requirement

11.4.2

"Internal penetration testing is performed", "By a qualified internal resource or qualified external third-party", and "Organizational independence of the tester exists (not required to be a QSA or ASV)"

"At least once every 12 months" and "After any significant infrastructure or application upgrade or change"

11.4.3

"External penetration testing is performed", on the same terms

"At least once every 12 months" and "After any significant infrastructure or application upgrade or change"

11.4.4

Exploitable vulnerabilities and security weaknesses are corrected, and "Penetration testing is repeated to verify the corrections"

After each test

11.4.5

"If segmentation is used to isolate the CDE from other networks, penetration tests are performed on segmentation controls"

"At least once every 12 months and after any changes to segmentation controls/methods"

11.4.6

The same segmentation testing, as an additional requirement for service providers

"At least once every six months and after any changes to segmentation controls/methods"

Requirement by requirement detail is in PCI DSS penetration testing.

Other rules, stated as they are written:

  • NYDFS 23 NYCRR 500.5 requires covered entities, other than the smaller entities that section 500.19 exempts, to conduct "penetration testing of their information systems from both inside and outside the information systems' boundaries by a qualified internal or external party at least annually." See NYDFS penetration testing requirements.

  • NIST SP 800-53 Rev. 5, control CA-8 reads "Conduct penetration testing" at an organization-defined frequency on organization-defined systems, so the interval comes from the program that adopts the control, not from the catalog itself.

  • The HIPAA Security Rule, as in force on 1 November 2026, sets an evaluation standard for covered entities and business associates at 45 CFR 164.308(a)(8): "Perform a periodic technical and nontechnical evaluation". The text does not name penetration testing. See HIPAA penetration testing requirements.

  • SOC 2 and ISO 27001 have their own guides: SOC 2 penetration testing and ISO 27001 penetration testing requirements.

Beyond the calendar, test again after the changes that move the attack surface: a new remote access system, a merger or new site, a domain migration, a redesign of segmentation, or a move of workloads to the cloud. How often to do penetration testing covers cadence, and continuous penetration testing covers the alternative to a single annual window.

How to choose a network penetration testing provider

PCI DSS v4.0.1 offers two considerations for choosing a tester. The first is "Specific penetration testing certifications, which may be an indication of the tester's skill level and competence." The second is prior experience, including "the type and scope of prior engagements". For network work, six checks do most of the sorting:

  1. Who will test. Ask for named testers and their certifications, and whether they are employees.

  2. A sample network report. Look for an attack path narrative, not a list of hosts and CVE numbers.

  3. Start positions. Ask where the internal test starts and how many positions the quote includes.

  4. Active Directory depth. Ask whether paths are proven or only listed by a collection tool.

  5. Segmentation. Ask whether it is in the quote, from which networks, and what statement the report makes.

  6. Retest. Ask whether it is included, and for how long after the report.

Providers are compared against these points in the best network penetration testing companies of 2026, and for internal and Active Directory depth in the best internal network and Active Directory penetration testing companies. The pentest and red team RFP question bank turns the checks into scored questions.

Where Stingrai fits

Stingrai is a CREST-accredited penetration testing company, accredited for both Penetration Testing and AI-Enabled Penetration Testing, offering fully human-led and hybrid (human penetration testers plus AI agents) penetration tests, delivered by experienced penetration testers who are also world-class security researchers and bug bounty hunters. Founded in Toronto, Canada in 2021, with an office in London, it works with companies from startups to enterprises in healthcare, financial services and SaaS.

Network engagements are human-led by two named penetration testers from a team holding OSCE³, OSEP, CRTO, CREST CRT and CISSP certifications, and every report is reviewed by the team lead, who has 16 years in penetration testing, red teaming and exploit development, and by an engagement partner. The team has published 18 CVEs.

  • External and internal network testing: the network penetration testing service covers the internet-facing perimeter, VPN and edge appliances, internal hosts and services, lateral movement between hosts and VLANs, and segmentation, black, grey or white box, following PTES and NIST SP 800-115.

  • Active Directory: the Active Directory security assessment starts from an ordinary domain user and proves the paths to control of the directory through Kerberos, delegation, access control lists and certificate services.

  • Wi-Fi: the Wi-Fi security assessment runs on-site or remotely with a shipped Wi-Fi Pineapple device, for as many locations as you choose.

  • Beyond the network: red teaming and purple teaming test detection and response once the network has been tested and fixed.

Findings reach the PTaaS platform as they are confirmed, with direct chat with the assigned penetration testers and Jira, Slack and GitHub integration. Retesting is included, and the report and attestation letter give penetration testing evidence for your PCI DSS, SOC 2, ISO 27001 and HIPAA programs. Engagements run as one-time annual tests or as continuous programs. Network, Active Directory and wireless work is scoped per engagement, and Stingrai's published fixed prices cover one web application and associated APIs (pricing).

Frequently Asked Questions

What is network penetration testing?

Network penetration testing is an authorized, time-boxed attack on an organization's network, carried out by penetration testers to prove how far a real intruder could get. It covers the internet-facing perimeter, the internal network, Active Directory, segmentation between zones, Wi-Fi and the links into the cloud. Weaknesses are exploited under agreed rules to confirm they are real, and the report shows how they chain into attack paths, with evidence and fixes.

What are the types of network penetration testing?

There are six. External testing starts on the internet with no credentials and targets the perimeter. Internal testing starts inside the network and measures what an intruder can do after the perimeter fails. Active Directory testing proves the routes from an ordinary domain account to control of the directory. Segmentation testing checks that networks outside a protected zone cannot reach into it. Wireless testing checks whether Wi-Fi is a route onto the wired network. Cloud-connected testing covers the identity and network links between the corporate network and the cloud.

What is the difference between network penetration testing and a vulnerability scan?

A vulnerability scan uses automated tools to list possible weaknesses across many hosts. A network penetration test is a manual process in which testers exploit weaknesses to confirm they are real and chain them to show how far an attacker could get. NIST SP 800-115 puts it this way: vulnerability scanners check only for the possible existence of a vulnerability, while the attack phase of a penetration test exploits the vulnerability to confirm its existence. PCI DSS v4.0.1 requires both and treats them as separate requirements.

What is the difference between a network penetration test and a red team engagement?

A network penetration test covers a defined scope as fully as time allows, usually with the defenders informed, and reports every exploitable weakness and attack path it proves. A red team engagement pursues agreed objectives covertly, over weeks or months, to measure whether the organization detects and responds. NIST SP 800-53 describes red team exercises as extending the objectives of penetration testing. Most organizations test and fix the network first, then run a red team engagement.

How long does a network penetration test take?

It depends on scope. Stingrai's published typical figures are 1 to 5 testing days for external testing and 1 to 10 testing days for internal testing, driven by live hosts, subnets and sites, the size of Active Directory and the number of start positions. Calendar time is longer than testing time because authorization, access set-up, report review and the retest take days of their own.

How much does network penetration testing cost?

Cost follows the number of testing days the scope needs, so it is set by live hosts and IP ranges, subnets, VLANs and sites, the Active Directory footprint, start positions, segmentation testing and whether testing is remote or on-site. Stingrai's network penetration testing page says a network penetration test typically costs US$5,000 to US$40,000 and above, and that PCI DSS engagements that bundle internal, external and segmentation testing commonly land at US$12,000 to US$25,000. That is a typical range across external and internal network testing, not a package price: Stingrai scopes network engagements per engagement, quotes a fixed price and returns pricing within 24 hours of a quote request, with the retest included. As a public reference for rates, GSA's CALC+ tool listed 442 hourly ceiling rates for penetration tester labor categories on federal schedule contracts on 13 November 2026, from US$57.34 to US$320.56 with a median of US$156.29. These are labor-hour ceilings on government contracts, not the price of a network penetration test.

How often should network penetration testing be done?

At least once a year and after any significant change to the network. PCI DSS v4.0.1 requires internal and external penetration testing at least once every 12 months and after any significant infrastructure or application upgrade or change, and segmentation testing every six months for service providers. NYDFS 23 NYCRR 500.5 requires penetration testing from both inside and outside the information systems' boundaries at least annually. Organizations whose networks change often move to a continuous program.

Does PCI DSS require network penetration testing?

Yes. PCI DSS v4.0.1 Requirement 11.4 requires a documented penetration testing methodology (11.4.1), and internal (11.4.2) and external (11.4.3) penetration testing, each test at least once every 12 months and after any significant infrastructure or application upgrade or change. Exploitable findings must be corrected and retested (11.4.4). Where segmentation isolates the cardholder data environment, the segmentation controls must be tested at least once every 12 months (11.4.5), and at least once every six months for service providers (11.4.6).

What does a network penetration test report include?

A report includes each confirmed finding with severity, affected hosts, reproduction evidence and remediation guidance, an attack path narrative showing how access moved from the starting position toward the objective, an executive summary, and a statement of scope, coverage and method, with segmentation results where tested. After fixes are deployed, a retest updates the status of every finding.

Is network penetration testing safe to run on a production network?

It is designed to be. Testing is authorized in writing, rules of engagement set testing windows and techniques that are off limits, and exploitation is controlled and focused on proving impact. NIST SP 800-115 notes that the risk can be reduced by experienced testers but never fully eliminated, which is why planning, notification and named escalation contacts are part of every engagement.

Talk to Stingrai

Planning a network penetration test? Send your external ranges, internal subnets, domain and site counts and the start positions you want tested, and Stingrai will return pricing within 24 hours, with the retest included, as a one-time annual engagement or a continuous program. Get a quote or book a discovery call.

0 views

0

X

Related reading

AWS Security Assessment (2026): What It Checks, Multi-Account Scope and Cost
Network Security

AWS Security Assessment (2026): What It Checks, Multi-Account Scope and Cost

What an AWS security assessment checks, how it differs from a pentest and Security Hub, how to sample a multi-account organization, deliverables and cost.

22 min read

Azure Penetration Testing (2026): Microsoft Rules, Scope, Cost Drivers and Providers
Network Security

Azure Penetration Testing (2026): Microsoft Rules, Scope, Cost Drivers and Providers

Azure penetration testing in 2026: what Microsoft's rules of engagement allow, what testers check from Entra ID to AKS, how to scope it and cost drivers.

25 min read

Best External Penetration Testing Companies (2026): Perimeter, VPN and Edge Testing
Network Security

Best External Penetration Testing Companies (2026): Perimeter, VPN and Edge Testing

The best external penetration testing companies for 2026, compared on perimeter, VPN and edge device scope, attack surface discovery, retests and price.

18 min read

Contents

X