Industries · 01

SaaS & software evidence your enterprise customers will accept.

The deal is ready until the security questionnaire arrives. We test multi-tenant platforms and APIs the way an attacker would, and give you a report you can send to the buyer.

Overview

Your customers trust you with their data, and with their customers' data. One tenant reading another's records ends the relationship.

Most SaaS security reviews come from the outside in: a questionnaire, a request for your latest penetration test, a call with the buyer's security team. We test what they will ask about, with the depth that makes the answers true.

We are also a development team, so we read your architecture the way your engineers do. Tenancy boundaries, role models, API keys and background jobs get tested on purpose, not by accident.

Frameworks we work to

  • ISO 27001
  • SOC 2
  • OWASP ASVS
  • OWASP API Top 10
  • CSA CAIQ
  • GDPR

Risks

Where SaaS platforms
usually break.

What our testers look for first in SaaS platforms, from experience rather than a generic checklist.

  1. 01

    Tenant isolation

    One customer reading or changing another customer's data through an ID, an export or a background job.

  2. 02

    Role and permission models

    Users promoting themselves, or reaching admin features the interface hides but the API allows.

  3. 03

    APIs and integrations

    Public APIs, webhooks and API keys with more access than the customer who created them.

  4. 04

    Single sign-on

    SAML and OAuth set-ups that can be talked into logging an attacker into someone else's account.

  5. 05

    Cloud configuration

    Storage, IAM roles and CI secrets that turn one small bug into access to everything.

  6. 06

    Release speed

    Weekly releases that quietly undo last year's fixes, with no test in between.

Evidence

What you get asked for.
And what we give you.

The requests that usually trigger a test in this sector, and the evidence that answers them.

Asked forWhat it meansWhat we provide
Enterprise security questionnaireBuyers ask when you were last tested, by whom, and what was found and fixed.A recent report, an executive summary you can share, and a retest showing findings closed.
ISO 27001Annex A asks for technical vulnerabilities to be managed and for security testing in development.Independent test results and remediation evidence your auditor can review.
SOC 2Auditors look for evidence that vulnerabilities are identified and dealt with.A dated report, remediation tracking and retest results.
Customer audit rightsLarger customers may want to see your report or a summary before signing.A letter of attestation summarising scope, dates and outcome.

NoteWe are not an ISO 27001 certification body or a SOC 2 auditor. We provide the testing evidence those audits look for.

Built here. Tested here.

Before launch, our own penetration testers attack what we built.

Our testers spend their weeks breaking web apps, APIs and mobile apps for other companies. Before your launch they do the same to yours, and the developers who wrote the code fix what they find.

About our penetration testing →
Build
Laravel, React and Node.js developers
Break
Manual testing, CREST-aligned methodology
Fix
By the people who wrote the code
Retest
Before we sign off

FAQ

Questions

From SaaS teams. Anything else, call us.

A penetration test from the last twelve months covering the product they are buying, evidence that serious findings were fixed, and sometimes a summary they can keep on file. We scope tests so the report answers those questions directly.

Yes. Alongside the full technical report, you get an executive summary and can ask for a letter of attestation that confirms scope, dates and outcome without exposing details.

At least once a year, and after major changes: a new product, a new authentication model, an infrastructure move. Many SaaS teams test lighter and more often around big releases.

We prefer a production-like staging environment with realistic data and roles. Where only production will do, we agree windows, rate limits and off-limits actions first.

Yes. An independent test is evidence auditors expect to see. We are not the certification body or the auditor; we provide the testing and remediation evidence they review.

Tell us about your platform.
We'll scope the right test.

A security engineer or developer reads every enquiry and replies, not a salesperson.

  • Fixed quote after a short scoping call
  • NDA available before you share details
  • Remediation and retest on every security engagement

Domains are fine as plain text (app.example.co.uk).

We only use your details to reply to this enquiry. See our privacy policy.