Skip to content

AI prompt · Web pentesting

Prompt: remediation sheet for developers

Prompt that turns a technical finding into an actionable remediation sheet: root cause, fix steps for your stack, a confirmation test and references.

By Steven Carrier Published

Works with: Claude, other chat assistants

You are an application security tester writing for developers. Turn the technical finding below into an actionable remediation sheet.

Finding: {{finding}}
Technology and stack: {{stack}}
Remediation constraints: {{constraints}}

Structure the sheet as follows:
1. root cause: explain why the vulnerability exists, in one or two sentences, without simply restating the finding;
2. recommended fix: numbered steps tailored to the stated technology, with a short defensive code or configuration example where useful;
3. alternatives or compensating controls if the ideal fix conflicts with the constraints;
4. confirmation test: how a developer confirms the vulnerability is fixed, and how to prevent a regression (automated test, static analysis rule);
5. references: public documents to consult (OWASP, official documentation of the technology).

Do not provide any exploitation payload: describe the fix, not the attack. If information is missing to recommend a precise fix, ask rather than invent. Do not invent references or function names: flag anything you are unsure about.

Replace the highlighted variables before use.

This prompt helps move from a finding written for a tester to a sheet that a development team can act on without back and forth: the cause, the fix steps, and the test that proves it works. It complements the report writing described in the pentest report skill.

Fill in the variables

Variable Example
{{finding}} An authenticated user reads another customer’s invoices by changing the identifier in GET /api/invoices/{id} (insecure direct object reference)
{{stack}} Node.js REST API with Express, Prisma ORM, PostgreSQL, JWT authentication
{{constraints}} fix deliverable in the next minor release, no API contract break for existing mobile clients

Describe the finding with the elements from your report: the request involved, the observed behaviour, the impact. Without the technology, the model produces generic advice.

Review the output

  • Check that the root cause is the right one: a model readily proposes a superficial symptom fix (filtering an input) rather than the design flaw (missing access control).
  • Test code samples before passing them on: function names, library options and versions may be inaccurate.
  • Check every reference against the official documentation or OWASP. Remove any you cannot find.
  • Replay the confirmation test yourself on a staging environment before closing the finding.
  • Do not paste into the prompt any client detail (domain names, secrets, personal data) that your engagement agreement does not allow you to share with an AI service; anonymise screenshots and requests.

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.