| Scoping and authorization | Agree the applications and hosts, the environment, testing windows, request-rate limits, roles in scope, and what is out of scope. Written authorization has to come from whoever controls each asset, including a hosting or third-party service when its terms require it. Authorized testing only happens inside the written scope. | This phase sets which OWASP Web Security Testing Guide (WSTG) categories can be exercised later. It does not itself test the application. | You provide written authorization, the in-scope applications and hosts, the roles to test, a named contact, and any environment or window constraints. You receive a written statement of work and rules of engagement. |
|---|
| Reconnaissance and mapping | Walk the in-scope application as an anonymous user and, when accounts are agreed, sign in with each agreed role. Map pages, features, and API calls, and note where permissions and tenant boundaries should apply. | Planned against WSTG information-gathering and configuration activities, and against the authentication and identity surfaces that were agreed. | You provide reachability for the systems in scope, the agreed test accounts, and API documentation if you have it. When between-user checks are in scope, that usually means more than one account in the same role, so those checks can be compared. Mapping usually informs later phases rather than arriving as a standalone deliverable. |
|---|
| Manual testing | Work through the mapped surfaces by hand, using tooling to widen coverage and flag candidate issues, then review those candidates by hand. Compare what each agreed role can reach. A logged-out-only scope stays on the public surface named in the statement of work; between-user, cross-tenant, and role privilege checks need the agreed accounts. The scope-choice table later on this page shows that difference. | Planned against WSTG categories such as authentication, authorization, session management, input validation, business logic, client-side testing, and API testing, as they apply to the agreed scope. Findings are mapped to an OWASP Top 10 category where one applies. When you want a requirements baseline, agreed ASVS requirements and verification level can be used as well. | You keep the agreed accounts and environment available. Manual testing is typically part of the engagement, not a separate handoff. |
|---|
| Exploitation within the rules of engagement | Where agreed, a tester carefully confirms impact inside the agreed scope, accounts, and window, and stops once impact is confirmed. If authorized access is obtained during a logged-out-only test, further authenticated work follows the agreed rules of engagement; it is not assumed from that scope. | Confirmation is for the candidate issues found in the agreed areas, not a second pass through every WSTG category. | You provide any mid-test decisions the rules call for. If a critical-severity issue is confirmed, the rules of engagement usually set how the named contact is told during testing. |
|---|
| Reporting | Document each validated finding with steps to reproduce, business impact, severity, and remediation guidance. Where a Top 10 category applies, the finding is mapped to it. | The report covers confirmed findings in the applications and APIs agreed in scope, at the same level of detail described later on this page. | You receive the written report and a readout with your team. A penetration test is not a compliance certification. It shows what was found inside the agreed scope and window. |
|---|
| Retest | A retest, when included, returns to the original confirmed findings, not a second full test of every page or endpoint. | Only the findings agreed for retest, not a new assessment of every WSTG category. | Retest terms set in the statement of work. You provide notice that fixes are ready when a retest is part of that agreement. You receive whatever that agreement sets. |
|---|