Skip to content

AI prompt · Web pentesting

Prompt: web application test plan

Prompt that builds a web application test plan aligned with the OWASP WSTG from your scope, application type and engagement constraints.

By Steven Carrier Published

Works with: Claude, other chat assistants

You are an application security tester. Prepare the penetration test plan for the application described below, aligned with the OWASP Web Security Testing Guide (WSTG).

Authorised scope: {{scope}}
Application type: {{application_type}}
Engagement constraints: {{constraints}}

For each WSTG category relevant to this application (information gathering, configuration and deployment, identity management, authentication, authorisation, session management, input validation, error handling, cryptography, business logic, client side, API):
1. list the tests to run with their WSTG identifier;
2. give their priority (high, medium, low) for this type of application;
3. state the prerequisites (accounts, roles, test data);
4. flag the tests to exclude or adapt because of the constraints.

Finish with an effort estimate in days per category, then the list of questions to ask the client before starting. Do not suggest any test outside the stated scope.

Replace the highlighted variables before use.

This prompt drafts the outline of a web penetration test before it starts: which WSTG tests to run, in what order of priority, and with what prerequisites. It helps at pre-sales to price an engagement, and at kick-off to split the work between testers.

Fill in the variables

Variable Example
{{scope}} https://staging.example.com and its /api/v2 API, excluding the back office
{{application_type}} single-page appointment booking application with online payment
{{constraints}} grey box, two accounts (patient, practitioner), no load testing, Monday to Friday, 9 am to 6 pm

The more precise the scope and constraints, the more usable the plan. Reuse what you agreed with the penetration test scoping checklist.

Review the output

  • Check every WSTG identifier against the official guide: a model may invent or mix them up.
  • Adjust priorities with what you know about the client and the model does not: incident history, regulatory requirements.
  • Treat the effort estimate as an order of magnitude, not a commitment.
  • Do not paste into the prompt any client information that your engagement agreement does not allow you to share with an AI service.

Sources

Related resources

  • AI prompt · Web pentesting

    API test plan prompt

    Prompt that builds an API test plan from an OpenAPI excerpt: endpoints by risk, authorisation matrix and tests per OWASP API Top 10 category.

    Published

  • Cheatsheet · Web pentesting

    Burp Suite cheatsheet

    Burp Suite for an authorised web test: proxy and CA certificate, scope, HTTP history, Repeater, careful Intruder use, Decoder and evidence export.

    Published

  • AI prompt · Web pentesting · Infrastructure and AD pentesting

    Critical vulnerability alert prompt

    Prompt that drafts the urgent client notification when a critical vulnerability is found during testing: facts, impact and immediate containment advice.

    Published

BEAROPS

Need a penetration test?

BEAROPS experts test your applications, infrastructure and cloud, black box or grey box, following OWASP, NIST and ANSSI guidance.