Assumed breach · Active Directory · Lateral movement
Internal Infrastructure Penetration Testing
If an attacker gets onto one laptop, how far can they go? We test from inside your network, assuming a breach or an insider, to find the paths to domain admin and your most sensitive systems.
- Active Directory attack paths
- Lateral movement
- Segmentation tested
In one sentence
What is internal infrastructure penetration testing?
Internal infrastructure penetration testing simulates an attacker or insider who already has a foothold in your network, to find the lateral movement, privilege escalation and segmentation weaknesses that lead to your most important systems.
Most serious breaches involve an attacker moving through the internal network after the first compromise. We show the exact path, and the smallest change that breaks it.
Where we can start
- A network port in your office
- A standard employee laptop or account
- A virtual machine in your network
- A remote VPN connection
Scope
What we test
The paths from one compromised device to the systems that matter.
Active Directory
Misconfigured permissions, delegation, Kerberos weaknesses and other paths to domain admin.
- Permissions
- Delegation
- Kerberos
Lateral movement
How an attacker moves between systems using credentials, sessions and remote services.
- Credentials
- Remote services
- Sessions
Privilege escalation
Local and domain privilege escalation on servers and workstations.
- Local admin
- Domain admin
- Services
Segmentation
Whether sensitive networks are really separated from user and guest networks.
- Network zones
- Firewalls
- VLANs
Legacy protocols
Name resolution, authentication and file sharing protocols that leak credentials.
- LLMNR
- NTLM
- SMBv1
Sensitive data exposure
File shares, databases and systems that hold data more people can reach than should.
- File shares
- Databases
- Backups
Approach
Testing approaches based on access
Choose how much you share with us. More context means deeper coverage in the same time.
No prior knowledge
Black box
We plug into the network with no account, as a visitor or intruder would.
Accounts and some context
Grey box
We start from a standard employee account and laptop, as after a phishing attack. This is what most clients choose.
Full access
White box
With network diagrams and configuration access, we also review segmentation and Active Directory settings in depth.
Engagement
How we work with you
Scope online
Describe what you need in Flint, our scoping platform. Answer only the questions that apply.
Proposal, signed online
Effort, price and the statement of work are built from your answers.
Ready for day one
Authorisation, test accounts and rules of engagement are agreed before testing starts.
Senior-led testing
Certified consultants lead the test. Our own AI framework, Striker AI, takes on the repetitive work.
Report and retest
Your report is ready in Slate, our client portal, within 48 hours of testing ending.
What you receive
Everything stays in one place, in your own client portal.
- A report in Slate within 48 hours of testing ending
- Every finding with evidence, a risk rating and a fix
- An executive summary for leadership
- Retests you can request finding by finding
- Downloads as PDF or Excel
- Evidence you can hand to your auditors
Standards
Standards we test against
So your results stand up with auditors, clients and regulators.
- CREST guidance
- MITRE ATT&CK
- CIS Benchmarks
- ISO/IEC 27001
- NIS2
- PCI DSS
Where does an internal test start?
Is this the same as an assumed breach red team?
Will testing disrupt our network?
Can you test on site and remotely?
When will we receive the report?
Contact
Tell us what you need to test
A senior tester reads every message and replies directly.
What happens next
- A senior tester replieswith any questions about your scope.
- You scope it in Flintor on a short call, if that is quicker.
- A proposal you sign onlinewith effort, price, dates and the statement of work.
Prefer email? Write to [email protected]
