Network Pentest Readiness Check
Fifteen yes/no questions that measure how ready your network infrastructure is for external and internal penetration testing.
- 15 questions
- ± 6 minutes
What this questionnaire covers
Questions are grouped by area. Open any area to see its questions before you start.
How the score is read
The score is the percentage of yes answers across all questions, mapped to one of these three levels.
- 0–39%
Not Test-ready
Basic network scope and controls are not ready. Tidy the asset inventory, segmentation and device patching first so testing focuses on the real weaknesses.
- 40–74%
Partially Ready
Your network is ready to be tested with some caveats. Complete the lowest-scoring areas before testing begins.
- 75–100%
Test-ready
Your network is ready for effective penetration testing. Next: agree the scope, rules of engagement and schedule.
Network scope5 questions
- Is the inventory of public IP addresses, internal network ranges, and critical devices (firewalls, routers, servers) complete?
- Is a network topology diagram (segments, DMZ, VLANs) available and current?
- Have external and internal testing windows been agreed without disrupting operations?
- Does testing cover both the external perimeter and the internal network, assuming an attacker has already gained a foothold?
- Are rules of engagement and emergency escalation contacts defined before testing begins?
Segmentation and perimeter controls5 questions
- Is the network segmented (VLAN/firewall) between critical zones, the DMZ, and general users?
- Are firewall rules reviewed periodically with least-privilege applied?
- Is remote access (VPN, RDP) protected by MFA and restricted by source?
- Are network devices and servers patched within severity-based SLAs?
- Have default credentials on network devices (routers, switches, management interfaces) been changed and audited?
Detection and follow-up5 questions
- Are IDS/IPS or network traffic monitoring active and watched?
- Are network device logs (firewall, switch, VPN) sent to a SIEM or centralised logging platform?
- Is wireless network security (WPA2/3-Enterprise, guest network isolation) applied?
- Have findings from previous network pentests been remediated and re-verified?
- Is every finding tracked in a central register with an owner and deadline?
Frequently asked questions
What is the difference between external and internal pentesting?
External pentesting simulates an attacker coming from the internet toward the public perimeter. Internal pentesting simulates an attacker already inside the network, such as an insider or a follow-on breach, and tests lateral movement.
What methodology does network pentesting follow?
The Penetration Testing Execution Standard (PTES) and NIST SP 800-115 for the technical framework and reporting.
Does the internal IT team need to know before testing starts?
Usually yes, so they do not mistake it for a real incident. The exception is an unannounced red team simulation approved by top management to test detection capability.
How long does a network test take?
Usually 1 to 2 weeks depending on the number of hosts, network segments, and whether external, internal, or both are tested.
Plan the network test with our team
Internal and external network pentests by an OSCP/OSWE-certified team following PTES and NIST SP 800-115, with a free retest.