See what the internet sees
External Network
Penetration Testing
We attack your perimeter the way a real adversary would, starting from zero knowledge, and show you exactly what is reachable and what it leads to. Every exposed host, port and service goes on a map first. Every scanner finding is confirmed by hand before it reaches your report.
Start outside with nothing
What the internet
can reach.
We test from zero knowledge by default, the way a real attacker starts, with partial or full knowledge available when you want depth over realism. Testing follows PTES and NIST SP 800-115, mapped to MITRE ATT&CK, and nothing reaches the report from a scanner unverified.
Phase 01 · Reconnaissance
Find what you own before we touch it.
A target picture built from public sources and checked against the scope you signed.
- Passive recon across DNS, certificate transparency logs and public records.
- Forgotten hosts and shadow IT domains flagged for your confirmation before testing.
- Written authorization and testing windows confirmed at kickoff.
Phase 02 · Reachability map
Map everything the internet can touch.
The internet reachability map: every live host, open port and service version, delivered first.
- Active host and port discovery across the in scope ranges.
- Service and version fingerprinting on everything that answers.
- Exposed admin panels, storage, APIs and dev endpoints called out.
Phase 03 · Exposed services
Test what answers, not what a scanner guesses.
Which exposures lead to a real foothold and which are noise, each proven or dismissed with evidence.
- Known exploit and missing patch testing on reachable services.
- Insecure protocols and misconfigurations confirmed by hand.
- SPF, DKIM and DMARC posture, spoofing exposure and DNS takeover risk.
Phase 04 · Authentication
Try the doors a real attacker tries first.
The login surfaces that fell and the ones that held, with gaps in multifactor coverage named.
- Weak, default and reused credentials on exposed login and VPN portals.
- Password spraying within lockout safe limits.
- MFA gaps on internet facing access.
Phase 05 · Foothold & proof
Prove the foothold, then stop at proof.
The attack narrative step by step, from first contact to the furthest point reached.
- Web flaws on reachable apps chained toward a network foothold.
- Impact demonstrated with a minimal safe artifact.
- Severity set by reachability and business impact.
Phase 06 · Report & readout
Hand you the fix list in priority order.
A report engineers can act on and a readout leadership can follow, with a retest option.
- Findings by severity with evidence and a specific fix for each.
- A tracker with one row per issue for engineering.
- A readout with the practitioner who ran the test.
Find what you own before we touch it.
A target picture built from public sources and checked against the scope you signed.
- Passive recon across DNS, certificate transparency logs and public records.
- Forgotten hosts and shadow IT domains flagged for your confirmation before testing.
- Written authorization and testing windows confirmed at kickoff.
Map everything the internet can touch.
The internet reachability map: every live host, open port and service version, delivered first.
- Active host and port discovery across the in scope ranges.
- Service and version fingerprinting on everything that answers.
- Exposed admin panels, storage, APIs and dev endpoints called out.
Test what answers, not what a scanner guesses.
Which exposures lead to a real foothold and which are noise, each proven or dismissed with evidence.
- Known exploit and missing patch testing on reachable services.
- Insecure protocols and misconfigurations confirmed by hand.
- SPF, DKIM and DMARC posture, spoofing exposure and DNS takeover risk.
Try the doors a real attacker tries first.
The login surfaces that fell and the ones that held, with gaps in multifactor coverage named.
- Weak, default and reused credentials on exposed login and VPN portals.
- Password spraying within lockout safe limits.
- MFA gaps on internet facing access.
Prove the foothold, then stop at proof.
The attack narrative step by step, from first contact to the furthest point reached.
- Web flaws on reachable apps chained toward a network foothold.
- Impact demonstrated with a minimal safe artifact.
- Severity set by reachability and business impact.
Hand you the fix list in priority order.
A report engineers can act on and a readout leadership can follow, with a retest option.
- Findings by severity with evidence and a specific fix for each.
- A tracker with one row per issue for engineering.
- A readout with the practitioner who ran the test.
Key benefits
Close the doors before someone tries them.
The reachability map shows every host, port and service the internet can reach, including the ones nobody remembered. If a forgotten server is out there, it lands on that list with an owner next to it.
Scanner output is a starting point, never a finding. A senior practitioner confirms each one by exploitation, so your team spends its time on exposures an attacker could actually use.
PTES and NIST SP 800-115, the same disciplined process every time. Send the report to an auditor, an insurer or a customer asking about your perimeter, and it stands on its own.
What you get
What lands on
your desk.
Three handoffs, starting with the map of what the internet can reach. Each one is written for the person who acts on it.
The document
The report
Executive summary, scope and method, the attack narrative, findings by severity with evidence and fixes, and the internet reachability map your team can keep current after we leave.
The working file
The findings tracker
One row per issue with severity, affected host and port, status, and an owner field. Engineering gets a list it can sort and close, not a PDF to transcribe.
The conversation
The readout
Time with the practitioner who ran the test. Findings in priority order, the top three actions, and plain answers for anyone who has to fund or approve the fixes.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Practical questions
Before we
touch anything.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
Testing runs in agreed windows, rate limited, and steers clear of anything you flag as fragile. Denial of service is out of scope by default. If something unexpected happens, we stop and contact your named point of contact before going further.
The external ranges and domains in scope, written authorization signed by someone with authority over those targets, and a named contact reachable during testing windows. Zero knowledge means we bring the rest.
That is common after growth or an acquisition. We can add external attack surface discovery before testing, hunting for forgotten servers and shadow IT domains, and you confirm ownership before anything new goes into scope.
Evidence is captured minimally, stored encrypted, and destroyed on a schedule we put in writing. Findings go only to the people you name, and the report describes exposed data without reproducing it.
A retest is a defined option, scoped with the engagement. After your team fixes what we found, we test each item again, confirm whether it closed, and issue an addendum with before and after status.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








