Cybernion
← Insights

Security

Network Penetration Testing Explained

10 Sept 2026 · Updated 10 Sept 2026

Network penetration testing targets the network layer, from internet-facing systems to internal infrastructure. An external test approaches from outside the perimeter; an internal test simulates an attacker already inside. Together they map the path from initial access to sensitive data, which is what a real attacker would walk. The ASD ISM recommends annual testing for systems handling sensitive information and the Essential Eight’s patching and segmentation controls are directly verified by network tests.

Network penetration testing answers a specific question: if an attacker can reach the network, what can they get to? It traces the same path a real attacker would follow, from the first point of contact through the network to the data or systems that matter most.

What network penetration testing covers

A network penetration test targets the infrastructure layer: the devices, services, protocols and connections that make the network function. This includes internet-facing systems such as firewalls, VPN gateways, mail servers, remote access services and edge devices; internal network infrastructure such as routers, switches, domain controllers and file servers; and the logical segmentation between network zones.

Network testing is distinct from web application penetration testing, which focuses on the logic of a single application, or API penetration testing, which focuses on API endpoints. A network test is concerned with how the infrastructure holds up, how systems connect, and how far an attacker who gains a foothold can travel. In practice, most full-scope engagements combine network and application testing, because an attacker on the network will also target the applications running on it.

External versus internal testing

The distinction between external and internal testing is fundamental to understanding what is being assessed.

External network penetration testing approaches the network from outside the perimeter, the way an attacker on the internet would. The tester has no credentials and no inside knowledge, and they target everything visible from the internet: firewall rules, exposed service ports, VPN and remote access endpoints, publicly accessible infrastructure, and any service listening on a public IP address. The test establishes what an opportunistic attacker or a motivated adversary who has researched the target could reach and exploit without any prior access.

Internal network penetration testing starts from inside the network perimeter, simulating an attacker who has already gained a foothold. This could be via a phishing attack, a compromised device, an insider threat, or physical access to a network port. Once inside, the tester attempts to discover internal systems, exploit vulnerabilities to escalate privileges, move laterally across network segments, and reach high-value targets such as domain controllers, databases and sensitive file shares. The test answers the question that many organisations fail to ask: after a breach, how much can an attacker reach?

Both types are commonly combined in a full-scope assessment. External testing establishes the perimeter exposure; internal testing establishes what follows a perimeter breach.

What testers look for

Network penetration testing looks for a class of vulnerabilities specific to network infrastructure and connectivity. Common findings include:

Unpatched vulnerabilities. Network devices and servers running software with publicly known, exploitable vulnerabilities are a consistent finding. Unpatched remote-code-execution vulnerabilities on internet-facing services are often the highest risk.

Unnecessary exposed services. Services that should not be accessible from the internet but are, whether due to firewall misconfiguration or default installs, are common. Management interfaces, database ports and administrative services on public-facing IPs are frequently found.

Weak or default credentials. Network devices, routers, switches, VPN concentrators and management consoles shipped with default passwords or configured with weak credentials are routinely discovered during testing.

Insecure protocols. Services running Telnet, FTP, SNMPv1/v2, or other protocols that transmit credentials or data in plaintext are a consistent finding, particularly on older infrastructure.

Network segmentation weaknesses. A flat network where all systems can communicate with all other systems provides no containment once an attacker is inside. Testers look for the ability to move from one network zone to another, for example from a guest network to the corporate network, or from a workstation to a server that should only be reachable by administrators.

Weak authentication on remote access. VPN and remote desktop services without multi-factor authentication, or with weak credentials, are high-priority targets for external testers.

Detection gaps. Testers observe whether monitoring and alerting systems detect attack activity. A test that goes entirely undetected by the SIEM (Security Information and Event Management) or the EDR (Endpoint Detection and Response) is a finding in its own right.

The methodology

Network penetration testing follows a structured methodology aligned with recognised standards including NIST SP 800-115 and PTES (Penetration Testing Execution Standard). The four phases are:

  1. Planning. Scope is defined, including which IP ranges, systems and network segments are in scope. Rules of engagement are agreed, including notification contacts in case a critical issue is found during testing.

  2. Discovery. The tester maps the network, identifies live hosts, discovers open ports and services, and fingerprints operating systems and software versions. This phase is largely reconnaissance.

  3. Exploitation. Identified vulnerabilities are exploited to confirm they are real and to establish access. Where access is gained, the tester attempts to escalate privileges, pivot to adjacent systems, and reach targets beyond the initial foothold.

  4. Reporting. All findings are documented with evidence, risk ratings, the potential impact of exploitation, and specific remediation guidance. Critical findings discovered during testing may be notified immediately rather than held for the report.

Framework requirements

The ASD Information Security Manual recommends annual penetration testing for systems handling sensitive information, and more frequent testing for higher-risk environments. Network segmentation, access control between zones, and vulnerability management for internet-facing systems are all ISM control areas that network testing directly verifies.

The Essential Eight includes patching internet-facing services within 48 hours of a critical patch release, and patching other systems within two weeks. Network penetration testing is the most direct way to verify that patching is effective in practice, not just in policy.

For IRAP assessments, the assessor examines network architecture, segmentation and access controls against ISM requirements. A recent penetration test report demonstrating that the network controls were tested and that findings were remediated is supporting evidence for the assessment.

ISO 27001 Annex A control A.8.8 addresses management of technical vulnerabilities, and control A.8.22 covers segregation of networks. Network penetration testing provides evidence that both controls are operating effectively.

Wireless network testing

Wireless penetration testing examines an organisation’s Wi-Fi infrastructure and may be scoped as part of the broader network test or as a separate engagement. It tests whether the wireless network uses strong encryption (WPA3 or WPA2-Enterprise), whether unauthenticated connection is possible, whether rogue access points are present, and whether an attacker connected to the wireless network can reach the corporate wired network. For organisations operating in shared spaces, client sites or environments with guest networks, wireless testing is an important component.

Cloud network considerations

Modern environments often include a mix of on-premises and cloud infrastructure, and cloud environments have their own network-layer considerations. Cloud penetration testing is a broader engagement, but from a network perspective it covers security groups and firewall rules in the cloud environment, exposed management APIs, and the network path between cloud and on-premises infrastructure. Cloud penetration testing is explored separately.

Cybernion provides penetration testing services covering network, web application and cloud environments, scoped to an organisation’s risk profile and regulatory obligations.

Frequently asked questions

What is network penetration testing?

Network penetration testing is security testing that targets the network layer, including internet-facing systems, internal network infrastructure, firewalls, routers, switches, VPNs and remote access services. A tester attempts to gain a foothold on the network and then move through it to reach sensitive systems or data, mimicking the path a real attacker would take after a breach. It differs from a web application penetration test, which focuses on a single application, in that network testing looks at the whole infrastructure and how systems connect.

What is the difference between external and internal network penetration testing?

External network penetration testing targets systems reachable from the internet, such as firewalls, web servers, VPN gateways, mail servers and remote access endpoints. The tester has no prior access and approaches from outside the network perimeter. Internal network penetration testing starts from inside the network, simulating an attacker who has already gained a foothold, whether through phishing, a compromised device or physical access, and tests how far they can move laterally and what they can reach. Both types are often combined in a full-scope engagement.

What does a network penetration test look for?

A network penetration test looks for vulnerabilities that allow an attacker to gain access or expand their access. Common findings include unpatched systems with publicly known vulnerabilities, services exposed unnecessarily to the internet, weak or default credentials on network devices, misconfigured firewalls or access control lists, unsecured protocols like Telnet or unencrypted SNMP, and network segmentation weaknesses that allow lateral movement from one part of the network to another. A test also assesses whether the monitoring and alerting systems detect the attack activity.

How does network penetration testing relate to Australian frameworks?

The ASD Information Security Manual includes controls on network management, network segmentation, and vulnerability management, and recommends annual penetration testing for systems handling sensitive information. The Essential Eight includes patching of internet-facing services and applications within 48 hours of critical patch release, and network testing verifies that patching is effective. ISO 27001 Annex A control A.8.8 addresses management of technical vulnerabilities. For IRAP assessments, network architecture and security controls are examined against ISM requirements.

Is wireless testing part of a network penetration test?

Wireless penetration testing may be included or treated as a separate engagement depending on scope. It tests the organisation’s Wi-Fi networks for weak encryption, the ability to connect as an unauthenticated user, rogue access points, and the ability to move from the wireless network to the wired corporate network. For organisations with significant wireless deployments, especially those in open or shared spaces, wireless testing is an important component of the overall network test.

Sources:

  1. NIST SP 800-115, Technical Guide to Information Security Testing, NIST Computer Security Resource Center, 2008
  2. Information Security Manual, Australian Signals Directorate, 2026
  3. Essential Eight, Australian Signals Directorate, 2026

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.