Shieldome SiegeShieldome Siege
Methodology

Internal vs External Penetration Testing

The distinction between internal and external testing is about where the tester starts, outside your network perimeter or already inside it, and that starting point changes what kind of risk the engagement actually measures.

External testing: what can be reached from the outside

An external test simulates an attacker with no existing access, working entirely from the public internet against whatever is externally reachable: public-facing web applications, exposed APIs, email infrastructure, and any service that should not be internet-facing but accidentally is. It answers the question: what can someone with zero inside access actually reach and exploit?

Internal testing: what happens after the perimeter is crossed

An internal test starts from a position already inside the network, simulating either a compromised device, a malicious insider, or an attacker who has already gotten past the perimeter through some other means, phishing, a compromised credential, a vendor connection. It answers a different, arguably more important question in a mature environment: once someone is inside, how far can they actually get?

Most real breaches do not stay at the perimeter. An attacker who gains any foothold, through phishing, a leaked credential, or a compromised third party, immediately becomes an internal threat. An organization that has only ever tested its external perimeter has never actually measured what happens after that first foothold is established.

Why relying on external testing alone creates a blind spot

A hardened external perimeter with weak internal segmentation and excessive lateral movement potential is a common, dangerous combination: hard to get into, but catastrophic once someone does, whether through a phishing email, a compromised vendor, or a misconfigured VPN. Internal testing is what actually measures that second half of the risk.

How they typically get combined

A common structure runs both in sequence within one engagement: an external test first, followed by an internal test that assumes a foothold has already been achieved, rather than requiring the external phase to succeed first. This measures the internal risk on its own terms, not contingent on whether the external test happened to find a way in during its allotted time.

Where an engagement starts, internally or externally, is really a subset of the broader black box, white box, and gray box decision, and both dimensions should be discussed explicitly when scoping any serious engagement.

See it in an actual tool

Shieldome Siege enforces scope on every action and gates exploit confirmation behind a human approval, with a tamper-evident audit log of the whole engagement.

Read the documentation