SaaS Penetration Testing

Is your SaaS platform keeping customer data separate?


Penetration testing for SaaS applications, APIs and supporting infrastructure. Assess tenant isolation, access controls, authentication and business logic to understand whether customers and their data are properly protected. Fixed-price, consultant-led testing.

Testing the security boundaries in SaaS

A SaaS platform can enforce authentication correctly and still expose one customer's data to another. We test the authorisation rules, tenant boundaries and business logic that determine what each user can actually access.

If you're preparing for your first assessment, our guide to scoping a web application penetration test covers what to prepare and what to expect.

Typical web application attack surface

  • Cross-tenant access
  • Role escalation
  • API authorisation
  • Workflow abuse
  • Integration boundaries

Note

The exact test cases are tailored to your application architecture, user roles and business-critical workflows.

When SaaS companies need a penetration test

Whether you're preparing for enterprise procurement, supporting a compliance programme or reviewing risk ahead of a major business milestone, a penetration test provides documented evidence of the security issues identified within an agreed scope.

An enterprise customer needs evidence of security testing

We provide technical findings and an executive summary that your team can use when responding to customer security reviews. See what a penetration test report should contain.

Your security programme needs documented testing evidence

Penetration testing can support your security assurance programme and provide evidence for auditors and customers. The testing scope and evidence required depend on your framework, applicable controls and auditor expectations. See our ISO 27001 penetration testing page for more details.

You need independent security assurance for due diligence

Security due diligence is increasingly common in funding rounds and M&A processes. A pentest report from a credible provider can help demonstrate that your team takes security seriously.

Enterprise deals require stronger security assurance

Enterprise buyers may request a recent report, scope details, remediation evidence and confirmation of the testing provider's independence. A pentest helps address these requests but does not guarantee acceptance by the buyer.

Scope of Testing

What a SaaS penetration test covers

SaaS applications are heavily API-driven, multi-tenant by design, and often tightly integrated with third-party services. Our testing is built around how your SaaS is actually built, rather than a generic web application checklist.
01

Web Application Testing

Manual testing informed by relevant OWASP guidance, covering business logic, broken access controls, privilege escalation, insecure direct object references and session management. See our web application penetration testing service for the full methodology.
02

API Penetration Testing

Where accessible within the agreed scope, we also assess undocumented endpoints and API functionality identified through application traffic and frontend analysis. See our API penetration testing service.
03

Authentication and Authorisation

Testing of login and account recovery flows, MFA, OAuth and SSO integrations, token validation, session handling and role-based permissions. We check whether users can access administrative functionality, impersonate other users or bypass intended authorisation rules.
04

Multi-tenancy and Data Isolation

We test whether users can access or modify records belonging to other tenants, bypass tenant-specific permissions or exploit inconsistencies in authorisation across APIs and application workflows. Testing is tailored to your tenancy model and the roles and resources within scope.
05

Third-party Integrations and Webhooks

We assess the security of in-scope integrations, including OAuth permissions, token handling, webhook authentication, request validation and trust boundaries between your application and connected services.
06

Infrastructure and Cloud Exposure

Cloud configuration reviews and broader infrastructure testing are separate scope items and will be priced explicitly in the proposal.

How It Works

From first contact to final report

You don't need a scope document prepared before reaching out.
01

Tell us what you need

Submit a quote request or book a scoping call with a rough idea of your application, API, number of user roles and any compliance context. We reply within one business day to confirm the scope, usually with a short questionnaire or a call.
02

Receive a written, fixed-price proposal

The proposal confirms the scope, methodology, timing, rules of engagement and a fixed price, rather than day rates. You accept when you're ready, and there's no obligation at any stage.
03

Testing begins, with direct access to your consultant

Testing typically involves 3-7 days of active assessment, depending on application complexity, user roles, API coverage and agreed scope, and larger platforms take longer. Your lead consultant will be involved in scoping and delivery, with direct access to the people conducting the assessment.
04

Report delivery and debrief

Technical and executive reports are delivered within 2 business days of testing completion, followed by a debrief call. Focused retesting of remediated findings is included, so you can confirm fixes hold before the report is shared externally.

What You Receive

Included in every engagement

  • Executive and technical reports

    An executive summary for leadership and procurement, plus technical findings with reproduction steps, risk ratings, business impact and practical remediation guidance.
  • Debrief and remediation guidance

    A call to walk through findings and remediation priorities with your technical and business teams.
  • Included retesting and findings tracking

    Focused retesting of eligible remediated findings, with results recorded in the Exploitr platform at no extra cost. Retesting scope and any exclusions are confirmed in the proposal.

Pricing

From £3,750

for SaaS penetration testing, web application and API included

Not sure which tier fits? A 30-minute scoping call is free and gets you a fixed written quote.

No obligation · Strictly confidential · Reply within one business day

Pricing Examples

First test
One application with one or two user roles and the API behind it. Typically before launch or a first customer security review
From £3,750
Growing product
Several user roles and core workflows, with the API behind them. Typically when enterprise customers, SOC 2 or ISO 27001 ask for a penetration test
From £4,750
Multi-product platform
Several applications, third-party integrations and a large API estate
From £8,750

Tenant isolation is tested at every tier.

Your exact price is fixed after a short scoping conversation. For more detail, see our web application penetration testing page.

What's Included

  • Testing usually starts within 2 to 3 weeks of agreement, depending on availability
  • In scope: the web application, its API, authentication, authorisation and cross-tenant access controls.
  • Not included: cloud configuration review and wider infrastructure testing, which are priced explicitly in your proposal
  • Free focused retesting included to verify remediation
  • Delivered remotely, against staging where possible
  • Report within 2 business days of testing completion, with a debrief call
  • Prices exclude VAT, and the fixed price is agreed before testing starts

Common Questions

SaaS pentesting: frequently asked questions

How SaaS penetration testing is priced, scoped and delivered, answered before you request a quote.

SaaS penetration testing starts from £3,750 for a first test of a single application with up to two user roles and two test tenants. The API behind the application is included.

A mid-sized SaaS application with several user roles, tenant isolation and complex business logic typically costs between £4,750 and £7,350, and larger multi-product platforms start from £8,750.

The final price depends on application complexity, the number of roles, tenants and workflows, API size, and any additional infrastructure testing. Your proposal will set out the agreed scope and fixed price before work begins. All prices exclude VAT.

We prefer to test in a staging environment where it adequately represents the production application. If production testing is necessary, we agree written rules of engagement, testing windows, prohibited actions and escalation contacts in advance. We take care to minimise disruption, but no active security test can guarantee zero operational impact.

Before testing begins, we'll need:

  • Test accounts for each user role to be tested (admin, standard user, etc.)
  • Two or more test tenants with representative user roles and test data, where applicable.
  • Access to a staging or test environment, or written permission to test production
  • API documentation if available (Swagger/OpenAPI, Postman, or equivalent)
  • A list of any systems or functionality that should be excluded from testing
  • An emergency contact in case of a critical finding or connectivity issue during testing

We discuss all of this during scoping and confirm it in the written proposal before any testing takes place.

Yes. Our reports are written with the understanding that they may be shared with third parties such as enterprise procurement teams, auditors, investors, and board members.

The executive report is designed for non-technical stakeholders, and the technical report supports SOC 2 Type II and ISO 27001 audit evidence and most enterprise security questionnaire responses.

An attestation letter is also included, for sharing with prospects who don't need the full report.

From initial contact to report delivery, a typical SaaS engagement runs as follows:

  • A reply within one business day, then a short scoping exchange before your fixed-price proposal
  • 2-3 weeks scheduling lead time
  • 3-7 days active testing, longer for larger platforms
  • 2 business days to deliver the report

If you have a compliance deadline or a deal closing, let us know upfront and we'll work to your timeline where possible.

Yes, the application-layer testing we conduct is cloud-agnostic.

If you'd like us to include a review of your cloud infrastructure configuration (exposed storage, overly permissive IAM, exposed admin interfaces), this can be added to the scope as an external infrastructure component. We'd discuss this during scoping and confirm it in the written proposal.

Our cloud penetration testing service covers cloud workloads and a CIS benchmark review of your accounts.

PCI DSS requires annual penetration testing, and ISO 27001 and SOC 2 auditors commonly expect it at least annually.

For fast-moving SaaS products, we'd also suggest testing after any significant architectural change, such as a new authentication provider, a major API version, or a new product area.

Our Pentest as a Service (PTaaS) offering is designed for teams that need ongoing testing coverage aligned with their release cadence.

Ready to scope your SaaS penetration test?

Tell us about your application and we'll reply within one business day to confirm the scope, then send a fixed-price proposal. No obligation at any stage.