Penetration testing · Internal network · Active Directory
Assume the phishingemail worked.
An internal test starts where most real intrusions do: with one ordinary user account, or one machine on the network. It shows how far an intruder could get from there, and what would stop them sooner.
CREST-certified testers£950 + VAT a dayReport in five working daysRetest included
Getting in is one thing. What matters is what can be reached from there.
Networks tend to be harder at the edge than in the middle. Inside, an attacker looks for the things that accumulate over years: a service account with a weak password, a share that everyone can read, an administrator who logs on to ordinary workstations, a trust between domains that nobody reviews. We work from a standard user account, or from a device placed on the network, and follow those paths under agreed rules until we reach what you have told us matters, or until your controls stop us. Both results are useful, and the second is the one we hope to report.
- Scope
- Workstations, servers, Active Directory and the network between them
- Starting point
- A standard user account, or an assumed-breach foothold
- Typical duration
- Two to six days of testing, plus one for reporting
- Typical price
- £2,850 to £6,650 + VAT
- Delivery
- Remote through a small appliance or VPN; on-site days add travel at cost
Coverage
What an internal test looks at
Credentials
Password policy, reuse between accounts, and credentials left in scripts, shares and group policy.
Active Directory
Kerberoasting, delegation, access control list abuse, certificate services and the trust relationships between domains.
Privilege paths
Where administrators log on, which accounts can reach which systems, and the shortest route from a standard user to control of the domain.
Segmentation
Whether the boundaries between user, server, management and operational networks do what the diagram says they do.
Patching and build
Unsupported operating systems, missing updates and local weaknesses that allow an ordinary user to become an administrator.
Data exposure
File shares, databases and backups readable by people who have no reason to read them.
Findings
What these tests usually find
- _01Service accounts with guessable passwordsAccounts created years ago for one application, with wide permissions and a password that never changes.Most common
- _02One local administrator password everywhereCompromise one workstation and the same password opens the rest.Credentials
- _03File shares open to everyoneScripts, spreadsheets and backups containing passwords, readable by any user.Data
- _04A flat networkNothing between a user's laptop and the servers that hold the data.Segmentation
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 |
|---|---|---|
| 50 internal hosts | 2 testing + 1 reporting | £2,850 + VAT |
| 100 internal hosts | 3 testing + 1 reporting | £3,800 + VAT |
| 500 internal hosts | 4 testing + 1 reporting | £4,750 + VAT |
| 1,000 internal hosts | 6 testing + 1 reporting | £6,650 + 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
Do you need to be on site?
Usually not. We send a small appliance to plug into the network, or connect over a VPN that you provide. On-site days are available where that suits you better, and add travel at cost.
What does assumed breach mean?
We begin as though one account or one device has already been compromised, because phishing and stolen passwords make that a realistic place to start. It spends the test days on what happens next, not on getting through the front door.
Will our SOC or endpoint protection see you?
It should, and that is worth knowing. If you want detection examined as well, say so at the scoping call and we will record what was noticed and what was not. For SOC365 clients, findings feed straight into detections so that the same path cannot be used quietly later.
Is it safe to run against live systems?
Yes, with care. We avoid techniques that risk locking accounts or interrupting services, agree anything intrusive in advance, and work to the rules of engagement set at the scoping call.
Start a conversation
Find the short route before someone else does.
A thirty-minute scoping call settles the starting point, the systems that matter most and the price.