Our services

A clearer view of risk.
A practical plan for what’s next.

Choose the application or workflow you need assessed. We’ll agree the coverage, handling arrangements and evidence your team needs before testing starts.

01

Web application
penetration testing

Understand risks across your web application’s functionality, data handling and supporting configuration, with clear priorities for remediation.

Application logic
Data handling
Configuration
02

API penetration
testing

Assess your API’s access controls, input handling, business logic and configuration, with practical findings for your team.

REST & GraphQL
Business logic
Usage controls
03

AI & LLM application
testing

Understand risks in your AI application’s inputs, data access, generated output and connected actions, with practical advice on what to fix.

Prompt injection
Data protection
Agents & tools
04

Mobile application
penetration testing

Assess your iOS or Android app’s storage, communications, platform interactions and backend controls, with clear advice on what to fix.

iOS & Android
Device & platform
Backend controls

What your team receives

Findings that are
ready for a discussion.

A useful report explains the technical risk and gives people a practical next step. We agree the format, recipients, readout and retest allowance during scoping.

Your assessment report

Clear findings.
A useful next step.

Executive summary
Key findings & implications
Summary of findings
An overview of the issues
Finding details
Understand, reproduce & remediate

Each detailed finding includes a description, reproduction steps, remediation steps and references.

Our process

One clear engagement.
From scope to retest.

Bring your product, deadline and review requirements. We’ll work through the details with you.

  1. Agree the right scope.

    Start with your product, deadline and reviewer. Confirm the environment, data, access and boundaries.

  2. Test the application.

    Use established security guidance as a baseline, then build on it with specialist testing of the agreed functionality, data flows and configuration. Document validated findings and the limits of the assessment.

  3. Make the findings useful.

    Walk through the results and practical remediation guidance with the people responsible for the next steps.

  4. Revisit the agreed fixes.

    Use the defined retest allowance to check the agreed changes and record the resulting status.

Before we begin

A few useful answers.

How much of the product will you test?

We agree the product version, environment, roles, workflows and exclusions before work starts. Coverage depends on that scope, rather than a promise to find every issue.

Can you support a customer security review?

We establish what the reviewer expects, including scope, report format and any provider credentials. The reviewer decides whether the resulting evidence meets its requirements.

What happens after the report?

The engagement defines the readout, clarification support and retest allowance. Your team implements the fixes; we assess the agreed changes within that retest scope.

How do you handle restricted information?

Private, self-hosted AI assistance. Assessment material is not sent to third-party model providers for that assistance. Storage, access, location, retention and contractual requirements are agreed separately. Read our handling approach.

Let’s talk through
your penetration test.

Tell us about your product, your deadline and the evidence your reviewer needs. We’ll agree the scope and handling arrangements before work starts.