Penetration testing
Manual penetration testing of infrastructure, applications and cloud services for organisations that do not need a CHECK test.
Request a quoteWhat a penetration test is
A penetration test is an authorised, controlled attack on your systems. It shows what a real attacker could reach and how serious that would be.
Testing is done by hand. We use standard tools to map your systems, then test manually for the flaws that automated scanners miss, such as weaknesses in authentication, access control and business logic.
Applications are tested to the OWASP Testing Guide and the OWASP API Security Top 10. Infrastructure is tested to the Penetration Testing Execution Standard (PTES) and NCSC guidance.
Testing is led by a consultant qualified as a Cyber Scheme Team Leader (CSTL Infrastructure), OSCP and CRTO.
You get:
- an executive summary that explains the risk in business terms
- a technical report with every finding rated by real-world risk
- prioritised steps to fix each finding
- step-by-step evidence so your engineers can reproduce each issue
- a debrief with the consultant who did the testing
- a free retest of critical and high findings once you have fixed them
What we test
External infrastructure
Your internet-facing systems tested the way a remote attacker would approach them: exposed services and management interfaces, VPN and remote access gateways, weak credentials and known vulnerabilities.
Internal infrastructure and Active Directory
What an attacker could do once inside your network: moving between systems, escalating privileges and the routes from a standard user account to domain administrator.
Web applications
Manual testing to the OWASP Testing Guide, covering injection, cross-site scripting, broken access control, authentication, session handling and business logic.
APIs
REST, SOAP and GraphQL interfaces tested to the OWASP API Security Top 10, covering authorisation, token handling, rate limiting and data exposure.
Mobile applications
iOS and Android apps tested to the OWASP mobile security standards, covering insecure storage, transport security, runtime manipulation and the services behind the app.
Cloud services
Microsoft 365, Azure and AWS tested for weaknesses in identity, privilege and data exposure, with reviews of configuration, containers and deployment pipelines.
Wireless and build reviews
Corporate and guest wireless networks, network segregation, and server and workstation builds reviewed against CIS Benchmarks.
Social engineering and red team exercises
Phishing assessments and goal-based exercises that test how your people, processes and defences respond to a realistic attack.
How a test runs
- Scope and plan: targets, rules of engagement and objectives are agreed.
- Reconnaissance: the attack surface is mapped.
- Enumeration: services, versions and weaknesses are identified and checked.
- Exploitation: controlled, manual exploitation proves real impact.
- Post-exploitation: privilege escalation, lateral movement and reach are assessed.
- Reporting: risk-rated findings, evidence and prioritised fixes.
- Retest: critical and high findings are retested once you have fixed them.
Every finding is checked by hand before it goes in the report, so you are not sent unverified scanner output.
Findings are rated by what an attacker could actually do with them. Low-rated issues that combine into a serious attack path are reported as one.
Common questions
How is this different from a vulnerability scan?
A scan matches your systems against known signatures. It cannot reason about business logic, combine weaknesses or prove what an attacker could achieve. A penetration test does all three by hand.
Will testing disrupt our live systems?
Testing is controlled and follows agreed rules of engagement. Anything intrusive is flagged in advance and can be scheduled out of hours. Denial of service and destructive techniques are out of scope unless you ask for them and authorise them.
Is a retest included?
Yes. A free retest of critical and high findings is included once you have fixed them, so you can show the issues were closed.
Do we need a CHECK test instead?
Central government bodies are expected to use a CHECK company. If you need one, we arrange it. Read who can carry out an IT Health Check.