Network penetration testing

See your network the way an attacker does

External, internal and cloud testing that maps every exposed service, proves what can be exploited and shows how far an attacker could move.

What we test

Coverage

External

  • Internet-facing hosts and services
  • VPN, remote access and email gateways
  • Exposed management interfaces

Internal

  • Assume-breach testing from inside your network
  • Active Directory and credential attacks
  • Lateral movement and privilege escalation

Cloud & segmentation

  • AWS, Azure and Google Cloud configurations
  • Firewall rules and network segmentation
  • Segmentation testing for PCI DSS scope

Methodology

Thorough by design

Most testers scan the top 1,024 ports. We examine all 65,536 TCP and UDP ports, including port 0, on every system in scope, because one missed service can change the whole picture. Our process draws on the OSSTMM (PDF), NIST SP 800-115 (PDF) and PTES methodologies, and meets PCI DSS penetration testing requirements.

  1. Reconnaissance

    Identify every system, data store and network component in scope.

  2. Enumeration

    Map the services running on each asset across all TCP and UDP ports.

  3. Research

    Find vulnerabilities, bugs and configuration weaknesses.

  4. Exploitation

    Escalate and validate each issue to determine real impact.

  5. Reporting

    Deliver audit-ready findings with prioritized fixes.

  6. Retest

    Confirm remediated findings are closed within 45 days.

Deliverables

What you receive

  • Executive summary written for leadership and auditors
  • Technical findings ranked by severity, with evidence and steps to reproduce
  • Remediation guidance tailored to your environment
  • A readout call to walk your team through the results
  • A retest of remediated findings within 45 days, included

FAQ

Common questions

How is this different from a vulnerability scan?

A scan is a quick, automated view and can miss a large share of real risk while reporting false positives. A scan is one step in our process; every finding is then researched and exploited by hand.

Will testing disrupt our operations?

We agree on testing windows and rules of engagement up front, and we don’t run exploits that could cause damage or make systems unresponsive.

How do internal tests work?

We can test on site, through a VPN connection or using a small testing device or virtual machine you deploy on your network.

How often should we test?

At least annually and after major changes. We can also set up a quarterly or monthly testing program.

Let’s map your network

Tell us what’s in scope, external, internal or cloud, and we’ll propose the right test.

Schedule a consultation (404) 819-9989