---
title: "How to Scope a SaaS Pentest"
description: "Build a clear web app and API penetration testing scope with assets, roles, tenant boundaries, exclusions, contacts, and written authorization."
canonical: "https://getpentester.com/blog/scope-saas-penetration-test/"
updated: "2026-11-18"
author: "CloudGuys"
published: "2026-11-18"
image: "https://getpentester.com/images/blog/scope-saas-penetration-test.jpg"
---

# How to scope a SaaS web app and API pentest

A SaaS penetration testing scope should name the approved apps and APIs, the environments, the roles and workflows to review, and the boundaries between organizations. It should also document exclusions, written authorization, the approved testing window, and who can pause the engagement.

## Start with the business question

Write one sentence about the decision the assessment needs to inform. For example, a CTO preparing a release might ask whether a new workspace export feature preserves the existing boundaries between tenant users and administrators. That gives the team a starting point for deciding which interfaces and account types belong in scope.

For an assessment covering broader application controls, use a requirements framework to agree on the depth of review. If a proposal names OWASP Application Security Verification Standard (ASVS), ask which version and requirements apply and how the provider will record partial coverage. [OWASP ASVS overview.](https://asvs.owasp.org/)

## What belongs in the scope brief?

- **Assets and environments.** List the web app, API, admin portal, and any other surfaces to include. Identify the environment for each and document differences that might affect how you interpret the results.
- **Roles and tenants.** Describe the distinct user, administrator, support, and service account permissions. Provide approved test accounts and synthetic data where practical.
- **Business workflows.** Prioritize flows where a failure could expose tenant data or affect money, account ownership, or access. State which functions the review must cover.
- **Exclusions and stop conditions.** Record assets owned by third parties, restricted actions, and any operational conditions that trigger a pause. Name the person authorized to approve scope changes.
- **Evidence and communication.** Agree on how urgent findings are communicated, how sensitive evidence is stored and shared, and what the final report and any follow-up should include.

## What does a useful scope handoff look like?

Consider a fictional SaaS team releasing organization-level exports. The brief names the staging web app and export API, two synthetic organizations, and two account roles in each. The team excludes its external identity provider and live delivery system. It records which tenant and role boundaries the assessment should address and assigns an engineering contact to handle access questions during the window.

Before kickoff, have the service owner review the scope, confirm the account access and environment, and sign off on written authorization. Record missing access as a coverage limitation so the team can decide whether to fix the setup or revise the scope. [NIST SP 800-115 covers planning and assessment logistics.](https://csrc.nist.gov/pubs/sp/800/115/final)

Use the [pentest cost guide](https://getpentester.com/blog/web-application-pentest-cost/) to turn the approved brief into comparable quotes. The [client preparation checklist](https://getpentester.com/docs/) covers what to bring to kickoff.

---

Sources in the Pentester repository: `docs/user-guide/scans.md`.
