Network Pentesting
Network vulnerabilities can lead to full system compromise. Identifying open ports and weak services is essential.
Who this is for
Engineering and security teams preparing for a release, a customer security review, or a procurement questionnaire — and anyone who needs to know what an attacker could actually reach.
Methodology
What We Test
- External Perimeter (Public IP space)
- Internal Network (Workstations, Servers, Printers)
- Active Directory (AD) and Domain Controllers
- Network Devices (Firewalls, Routers, Switches)
- VPN and Remote Access endpoints
- Wireless Networks (Wi-Fi)
How We Test
External: We simulate an outsider trying to breach the perimeter. Internal: We simulate a malicious insider or compromised host. We perform port scanning, service enumeration, exploit unpatched services, and attempt lateral movement and privilege escalation (e.g., Kerberoasting, LLMNR poisoning).
What You Receive
- Comprehensive list of open ports and services
- Verified vulnerabilities with evidence
- Attack path visualisation for every route we were able to prove, plus the paths we tested that held
- Prioritized patch and configuration management plan
How an engagement runs
-
Scope & authorisation
We agree exactly what is in scope, what is explicitly out, and the conditions under which we stop. Nothing starts without written authorisation from someone able to give it. NDA first if you want one.
-
Access & prerequisites
We tell you up front what we need — test accounts at each privilege level, a non-production environment where that applies, documentation, and a named technical contact. Missing prerequisites are the usual reason assessments slip.
-
Reconnaissance & threat modelling
We map the real attack surface and decide which paths are worth the time, based on how your system is actually built rather than a generic checklist.
-
Manual testing & validated exploitation
Testing is hands-on. Findings are reproduced before they are written up, so you are not sent unverified scanner output. Critical issues are raised as soon as we confirm them rather than held for the report.
-
Report & walkthrough
You get an executive summary your board can read and technical detail your engineers can act on — including reproduction steps, what we tested that held, and what was out of scope. We walk your team through it.
-
Retest
Once you have fixed the findings we retest them and confirm in writing what is closed. Retest scope and window are agreed in your scope document before the engagement begins.
Toolkit
- Nmap
- Metasploit
- Wireshark
- Nessus
- Responder