Skip to content

Cheatsheet · Web pentesting

Burp Suite: proxy, Repeater, Intruder and evidence for a web test

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

By Steven Carrier Published

Official website: Burp Suite

Burp Suite is an intercepting proxy: it sits between the browser and the application to observe, replay and modify HTTP requests. This sheet covers the features common to the Community and Professional editions; differences are flagged. Work only within a scope agreed using the penetration test scoping checklist. To test an API, see also the REST API testing methodology.

Connect the browser and install the certificate

By default, Burp listens on 127.0.0.1:8080 (Proxy tab, listener settings). The simplest option is Burp’s built-in browser, which is already configured. For a separate test browser:

  1. Set the browser’s HTTP and HTTPS proxy to 127.0.0.1 port 8080.
  2. With the proxy active, open http://burpsuite and download the CA certificate ("CA Certificate").
  3. Import it into the test browser’s certificate store, never into the system store of an everyday workstation.
  4. Use a browser profile dedicated to the engagement, so personal traffic does not mix with evidence.

Without this certificate, every HTTPS site will show an error. Remove the certificate and the profile at the end of the engagement.

Define the scope

Target > Scope > Include in scope : https://target.example/
Target > Scope > Exclude from scope : https://target.example/logout

Add to scope only the hosts authorised by the engagement letter, and exclude actions with side effects (logout, account deletion, bulk e-mail sending). In the proxy settings, enable the option that stops out-of-scope items being sent to the history and other tools: it reduces noise and protects against accidentally testing a third party (CDN, analytics service).

Read the HTTP history

The Proxy tab, HTTP history sub-tab, keeps every exchange. The filter bar lets you:

Filter Use
Show only in-scope items keep only hosts inside the scope
Filter by MIME type hide images, CSS and fonts
Filter by status code isolate 3xx, 401, 403 or 5xx
Filter by file extension hide certain static extensions
Filter by search term search for text in requests or responses
Show only parameterized requests see only requests with parameters

The history search box helps you find a specific trace (parameter name, error message, header). Leave interception off (Intercept is off) until you need to hold a request: the history is enough for observation.

Replay with Repeater

Repeater sends a request as many times as needed, modifying it on each attempt.

  • From the history: right-click, "Send to Repeater" (Ctrl+R).
  • Change one element at a time (parameter, header, method), then "Send" (Ctrl+Space).
  • Compare the status, size and duration of each response; the "Render" tab helps when reading an HTML page.
  • Name your tabs (double-click): one tab per hypothesis gives you replayable evidence.

To reproduce evidence outside Burp, right-click then "Copy as curl command": see the curl cheatsheet.

Intruder: the basics and the limits

Intruder automates sending series of requests while varying marked positions in the request.

Attack type Behaviour
Sniper one list, one position at a time
Battering ram one list, the same value in every position
Pitchfork one list per position, iterated in parallel
Cluster bomb one list per position, every combination

Engagement precautions, especially in production:

  • Work out the number of requests before starting, particularly with Cluster bomb: it is the product of the list sizes.
  • Set the attack’s resource pool to cap concurrent requests and add a delay between requests. The Community edition also deliberately throttles Intruder.
  • Never target a login or password-reset form without explicit agreement: account lockouts, real e-mails or SMS messages.
  • Watch for 429 and 5xx codes and stop the attack at the first sign of degradation.

For large-scale content discovery, a dedicated tool such as ffuf with a capped rate is better suited.

Compare and decode

  • Comparer: send two requests or responses (right-click, "Send to Comparer"), then compare them by words or bytes. Useful to tell apart two almost identical responses (existing user or not, access granted or denied).
  • Decoder: converts text to and from URL, HTML, Base64, hexadecimal and several other encodings, and computes hashes. It decodes, it does not interpret: a decoded token can be read, not "cracked".

Useful shortcuts

Shortcut Action
Ctrl+R send the selected request to Repeater
Ctrl+I send the selected request to Intruder
Ctrl+Space send the request in Repeater
Ctrl+U / Ctrl+Shift+U URL-encode / URL-decode the selection
Ctrl+B / Ctrl+Shift+B Base64-encode / Base64-decode the selection
Ctrl+Shift+P, R, I, T go to Proxy, Repeater, Intruder, Target

On macOS, replace Ctrl with Cmd. Shortcuts can be changed in the application settings; check them if one does not respond.

Project and evidence export

  • The Professional edition saves a project file (.burp): create one per engagement, named after the client and the date. The Community edition only offers temporary projects: export before closing.
  • For one request or response: right-click, "Save item", or paste into the report with a timestamp screenshot.
  • For a batch of exchanges: select them in the history, then "Save items".
  • To replay outside Burp: "Copy as curl command".
  • Redact secrets (tokens, session cookies, passwords) before putting evidence into a deliverable.

The project file contains all the traffic, including credentials and personal data: encrypt it at rest and destroy it according to the retention rules agreed with the client.

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

  • 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

  • Cheatsheet · Web pentesting

    curl cheatsheet (web testing)

    curl for an authorised web test: methods, headers, cookies, authentication, redirects, timing, Burp proxy, TLS, HTTP/2, JSON and file uploads.

    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.