Penetration testing · External infrastructure
What the internetcan see of you.
An external test looks at everything of yours that answers from the internet, the way an attacker with no inside knowledge would. It finds what is exposed, proves what can be done with it, and tells you what to close first.
CREST-certified testers£950 + VAT a dayReport in five working daysRetest included
Most intrusions begin with something that was reachable and did not need to be.
Your external estate is rarely the tidy list in the asset register. It includes the VPN gateway and the mail and web servers, and usually something nobody remembers commissioning: a test site, an old remote-access portal, a supplier's management interface. We start by finding all of it from public sources, agree the list with you, and then test each service by hand. Scanners are used to cover ground. The findings that matter come from a tester working out how two small weaknesses combine into a way in.
- Scope
- Internet-facing addresses, host names and the services on them
- Typical duration
- One to four days of testing, plus one for reporting
- Typical price
- £1,900 to £4,750 + VAT
- Access needed
- None: the test is run from outside, with your written authority
- Methods
- OSSTMM · PTES · findings mapped to MITRE ATT&CK
Coverage
What an external test looks at
Discovery
Hosts, subdomains and certificates found through open sources, DNS and certificate transparency, compared with the list you expected to see.
Remote access
VPN gateways, remote desktop and portals: authentication strength, lockout, legacy protocols and known vulnerabilities in the appliance itself.
Web and mail servers
Software versions, configuration, TLS and the administrative paths that have no reason to answer from outside.
Exposed administration
Management consoles, databases and device interfaces reachable from the internet, with default and weak credentials tried under agreed rules.
Email and DNS
SPF, DKIM and DMARC, zone configuration, and the records that give away internal naming.
Firewall behaviour
What the edge allows that the rule base never intended: unnecessary ports, over-broad rules and forgotten exceptions.
Findings
What these tests usually find
- _01Unsupported or unpatched edge softwareVPN appliances, web servers and mail gateways running versions with published exploits.Most common
- _02A system nobody knew was thereA test server, a retired portal or a supplier's device, still answering and outside the patching routine.Shadow IT
- _03Login pages without multi-factor authenticationRemote access or webmail protected by a password alone.Identity
- _04Information given away for freeInternal host names in DNS and certificates, software versions in banners, staff names in document metadata.Leakage
Cost
What it costs
Penetration testing is charged at one published rate, £950 + VAT a day, with one day added to every engagement for reporting, quality assurance and the debrief. The days follow the scope.
| Scope | Days | Price |
|---|---|---|
| Up to 8 live IP addresses | 1 testing + 1 reporting | £1,900 + VAT |
| 16 live IP addresses | 2 testing + 1 reporting | £2,850 + VAT |
| 64 live IP addresses | 4 testing + 1 reporting | £4,750 + VAT |
These figures come from the estimator on the penetration testing page, where you can change the numbers and combine this test with others; one reporting day covers the whole engagement. A scoping call confirms the days and turns the estimate into a fixed price.
Questions
Questions about this test
Will the test take our services offline?
It should not. Testing is manual and controlled, denial-of-service techniques are left out unless you ask for them, and anything that carries risk is agreed with you before it is tried. The rules of engagement are written down at the scoping call.
How is this different from a vulnerability scan?
A scan lists software with known flaws. A test asks what a person could do with them: whether the flaw is exploitable here, what it leads to, and how it combines with other weaknesses. The report contains only findings a tester has validated.
How often should it be done?
Most organisations test their external estate once a year, and again after a significant change such as a new remote-access system or a move to a new hosting provider. PCI DSS and many customer contracts set that as the minimum.
Can we check our exposure before committing to a test?
Yes, and you can do it yourself in a few minutes. The free External Exposure Report runs eight checks on a domain and grades the result. It is not a penetration test, but it shows the kind of thing one would look at first.
Start a conversation
Start with what is exposed.
A thirty-minute scoping call fixes the list of addresses, the rules of engagement and the price.