Skip to content
gradient overlay

Penetration testing

Penetration testing is a structured attempt to breach your cybersecurity systems using the same techniques an attacker uses. The aim is to identify weaknesses before they can be exploited and to provide a clear, honest account of what was found and how it can be resolved.

Types of penetration testing

The type of penetration testing we use depends heavily on your needs, your risk profile and your infrastructure.

We also deliver bespoke testing for projects with unique security requirements. If the service you are looking for isn’t listed, please get in touch for a discussion about your assurance needs.

Infrastructure testing is the most commonly requested type of penetration test. It covers the devices and systems that make up your network including endpoints, servers, routers, printers and everything in between. It can be scoped to a single area, but a penetration test of your entire organisation provides the best indication of your vulnerability.

Because a threat can come from anywhere, we test from both internal and external perspectives. An external test examines what an attacker could reach from outside your network whereas an internal test explores what can be accessed from within your network. Both approaches are valuable and many organisations benefit from running them together.

Web applications are among the most targeted entry points for attackers. They handle sensitive data, process payments and often connect directly to your core systems, which makes a vulnerability in one place a potential risk across your systems.

We perform penetration testing on web applications in line with OWASP testing methodologies. The OWASP approach is a structured, repeatable framework used to identify and document vulnerabilities in web and mobile applications.

Web application testing can be conducted on a one-off or recurring basis depending on how frequently your application changes, or the level of risk you are experiencing.

Whilst convenient for collaboration, cloud environments introduce security challenges that on-premises infrastructure does not. The most common vulnerabilities in cloud infrastructure relate to permissions and access.

We test Azure and AWS cloud environments for misconfigurations and attack paths, including account compromise, privilege escalation, lateral movement and data theft.

APIs can often expose sensitive data and provide an interface for authorisation controls. A weakness here can signpost an attacker to …

Our API penetration testing follows a similar methodology to web application testing and adds a greater emphasis on data exposure and privilege escalation, common vulnerabilities with APIs. Our OffSec-certified specialists assess your endpoints, thoroughly reviewing how they handle authentication, the data they return and whether access controls hold up under pressure.

We carry out build reviews for new deployments, identifying weaknesses before they cause a problem and collaborating with your team to ensure security is embedded in the deployment rather than applied as an afterthought.

Our team of penetration testing experts offers build reviews for most platforms, examining everything from Windows endpoints to Docker images. As well as working with new deployments, our consultation services are available when you are looking to make changes to an existing deployment while raising your security standards.

A vulnerability assessment uses automated scanning to identify missing patches and common misconfigurations across your systems. It is a practical starting point for organisations that want a baseline view of their exposure.

Whilst vulnerability assessments do not replace the judgment of a skilled tester to uncover complex chained vulnerabilities, it’s an efficient approach for identifying known security issues. We offer one-off and recurring assessments for small and medium-sized companies.

Need more than a one-off test?

If you have ongoing testing requirements throughout the year, a regular testing arrangement will likely be more cost-effective than booking engagements individually. Day rates are discounted, scheduling is simple and unused days roll over, providing flexibility to test when it makes sense to your organisation.

Arrangements start from two days per month and provide access to our full penetration testing suite. If regular testing suits your requirements, get in touch to talk through the options.

Get in Touch

How we work

Consistency built in

To balance between known and common weaknesses and novel attack paths, we have established Baseline Test Cases for each service offering. These consist of the attacks and weaknesses we believe should be tested every time. We are constantly growing the case list to ensure our service offerings remain in line with the cybersecurity landscape.

Discretion by default

Being trusted with matters of high security and sensitive information is a responsibility we take incredibly seriously. Whether we are protecting critical infrastructure or high-net-worth individuals, we operate with discretion by default and take extensive measures to protect your data on any engagements.

Senior oversight

Our team has extensive experience in offensive security and our specialists are all CREST or OffSec-certified. When our collaboration with you begins, you’ll meet a senior specialist who is dedicated to overseeing your engagement from start to finish. They will guide you through the process and answer any questions you may have.

gradient overlay
How do you calculate the number of days for testing?
When you request our penetration testing services, we’ll hold a scoping call to understand your testing and security requirements. We will ask you about the number of systems you would like to test, how many privilege levels you’d like us to test from and the level of assurance you require for each system and service in scope. From this, we calculate how long it will take to test each asset to the required level and turn this into a time estimate.
Why are your testing days only an estimate?
There is sometimes a variation between the time quoted to perform a test and the time it actually takes. This is because some assets have a smaller attack surface than expected, or a critical vulnerability found towards the end of the engagement may affect assets outside of scope, requiring additional investigation. In either case, our tests are billed on a time and materials basis and so we will only ever invoice you for the testing we have done, and we will never add additional testing time without your permission.
Why do you ask for credentials and antivirus exceptions for some tests?
Often the tools we use to validate if a vulnerability or misconfiguration exists are blocked by security products, meaning that our testers have to spend time evading security products instead of validating the root problem. We are committed to applying your budget effectively, and so we may ask for credentials or antivirus exceptions to allow us to address your vulnerabilities efficiently.
How do you access our systems for testing?
The way we access your system will depend on the type of test you have requested. Some tests require no setup, whereas for others we use physical and virtual appliances, VPNs or remote management tools. We will discuss the best options for you in advance of your test.
Will our systems be damaged or interrupted?
Whilst all forms of security assessment carry a risk of unexpected downtime, we take many measures to reduce this risk to the bare minimum. We will always seek your consent before attempting high-risk techniques and will never perform availability testing without requesting permission first.
gradient overlay

Want to get a bespoke quote? contact our team today