Offensive Security
Network Penetration Testing
External and internal network testing that establishes how far an attacker could actually get.
Overview
A network test should answer two questions: what is reachable from outside, and what happens once someone is inside. We answer both.
External testing enumerates your internet-facing estate, including the hosts nobody remembers deploying, and tests exposed services for misconfiguration, weak authentication and known-vulnerable software. Internal testing starts from an assumed foothold and pursues privilege escalation, credential exposure and lateral movement to show what an attacker could reach from a single compromised workstation or service account.
Testing is bounded by the agreed rules of engagement. Denial-of-service and destructive techniques are excluded unless explicitly authorised in writing.
Methodology
How the engagement runs from start to finish.
- Scoping, rules of engagement and written authorisation
- Host, service and version enumeration
- Authenticated and unauthenticated vulnerability discovery
- Manual verification and controlled exploitation
- Privilege escalation and lateral movement where in scope
- Segmentation and egress testing
- Evidence collection, risk validation and CVSS scoring
- Reporting, debrief and retest
Related
Often scoped alongside this
Web Application Penetration Testing
Manual, authenticated testing of your web application against the way real attackers approach it.
Learn more Offensive SecurityAPI Penetration Testing
Authorisation-focused testing of REST, GraphQL and internal APIs, guided by the OWASP API Security Top 10.
Learn more Offensive SecurityCloud Penetration Testing
Configuration and identity review of AWS, Azure and GCP environments, combined with hands-on attack-path testing.
Learn more
Ready to find the weaknesses first?
Tell us what you are building or what you need tested. We will come back with a scope, a timeline and a clear price, with no obligation.