Network penetration testing
We test your network the way an attacker would: from the internet-facing perimeter, from an assumed foothold inside, and across segmentation boundaries. Following PTES and NIST SP 800-115, a pentest confirms that a weakness can be exploited instead of only scanning for it.
Three perspectives
A penetration test confirms that a weakness can be exploited, not only that a vulnerability is present (NIST SP 800-115). We cover the external perimeter and the internal network from an assumed foothold. Just as important, we test segmentation by trying to cross it instead of only scanning it.
- External perimeter: internet-facing services, exposed assets and remote access
- Internal network: lateral movement, privilege escalation and Active Directory attacks
- Segmentation: actively attempting to reach the sensitive zone (CDE) from outside it
- Misconfigurations, weak services and credential weaknesses
- Insufficient input validation and exploitable service vulnerabilities
- Exploitation chained to demonstrate real, prioritised impact
A standards-based engagement
We follow the NIST SP 800-115 phases, where the attack phase loops back to discovery as new access is gained, and structure the engagement per PTES. Box type (black-, grey- or white-box) is agreed with you up front.
- 1
Planning
We agree scope, the threat model, targets and rules of engagement, and sign an NDA before any access.
- 2
Discovery
We enumerate hosts, services and trust relationships to build an accurate picture of the attack surface.
- 3
Attack
We confirm weaknesses by exploiting them, and go back to discovery whenever new access opens new paths.
- 4
Segmentation validation
We actively attempt to cross isolation boundaries into the sensitive zone, rather than relying on a scan.
- 5
Reporting & free re-test
You get a prioritised report including segmentation results; we re-test fixed issues at no extra charge, within the window set in the Statement of Work.
What you receive
A report structured along the lines of the PCI SSC penetration-testing report outline, with a dedicated segmentation section and the depth of our sample report.
- Executive summary, statement of scope (CDE vs non-CDE) and methodology
- Testing narrative and a dedicated segmentation-test results section
- Each finding: exploitability, evidence, steps to reproduce and remediation
- Severity scored with CVSS 3.1 and translated into business risk
- References to CVE and CWE, plus tools used and a cleanup statement
- Free re-test of remediated issues, within the window set in the SoW; optional confirmation letter (not a QSA attestation)
Grounded in PTES, NIST SP 800-115 & PCI guidance
External, internal and segmentation testing follows PTES and NIST SP 800-115. Segmentation testing checks isolation in practice and supports your PCI DSS Req 11.4 penetration-testing requirements. We provide readiness and testing; we are not a QSA and do not issue certifications. We can provide a confirmation letter, which is explicitly not a QSA attestation. Findings are scored with CVSS 3.1.