Penetration testing by people who do it for sport

Our engineers hold CEH, CPENT and LPT (Master), and place among the top teams in international capture-the-flag competitions. They test your systems by hand, the way a real attacker would.

What we test

Web applications and APIs
Tested against the OWASP Top 10 and the OWASP Application Security Verification Standard, including authentication, access control and business logic.
External and internal networks
What an attacker can reach from the internet, and how far they could go once inside.
Cloud
Configuration and access reviews of AWS, Azure and Google Cloud environments.
Mobile applications
iOS and Android apps and the services behind them.
Active Directory and identity
The attack paths from an ordinary account to control of the domain.
Social engineering
Phishing simulations that show how your people and your controls respond.
Red team and assumed breach
Goal-based exercises that test detection and response, not only prevention.
Vulnerability assessment and retesting
A broad sweep for known weaknesses, and a retest once fixes are in.
Secure code review and threat modelling
Finding design and code flaws before they ship.

A method your auditor will recognize

Every engagement follows published standards, so the work can be repeated, checked and explained.

PTES

The Penetration Testing Execution Standard sets the phases of the engagement, from scoping to reporting.

OWASP Testing Guide

The reference for testing web applications and APIs.

NIST SP 800-115

The U.S. National Institute of Standards and Technology guide to security testing and assessment.

One report, three readers

A penetration test is only as useful as its write-up. Ours is written for everyone who has to act on it.

Your engineers
Every finding comes with reproduction steps and a prioritized fix, so nobody has to guess how we got in.
Your executives
A short summary of what is at risk, how serious it is and what it will take to close.
Your auditor
Scope, method, findings and retest results laid out the way SOC 2 auditors ask for penetration test evidence.

How an engagement runs

  1. Scope

    We agree on targets, timing and limits, then sign the rules of engagement and an NDA before any testing starts.

  2. Test

    Our engineers attack the agreed targets by hand, and tell you straight away if they find something critical.

  3. Report

    You get the written report and a walkthrough call with the engineers who did the work.

  4. Retest

    Once you have fixed the findings we test them again and record the result for your auditor.

Tell us what you need tested

A scoping call takes about 30 minutes. You leave with a clear scope, a timeline and a fixed quote.