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
Scope of Testing
What a SaaS penetration test covers
Web Application Testing
API Penetration Testing
Authentication and Authorisation
Multi-tenancy and Data Isolation
Third-party Integrations and Webhooks
Infrastructure and Cloud Exposure
How It Works
From first contact to final report
Tell us what you need
Receive a written, fixed-price proposal
Testing begins, with direct access to your consultant
Report delivery and debrief
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
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.
