Skip to content
Tutorials Center
My learning

Topics

Lesson 38 of 38 ยท Projects and Practice

Burp Suite Practice Questions and Cheat Sheet

Review Burp Suite with a tool-by-tool cheat sheet, useful shortcuts, a vulnerability testing checklist, common mistakes, practice scenarios and a final self-test quiz.

You have covered the whole Burp Suite toolkit: the proxy, target and site map, Repeater, Intruder, Scanner, extensions, session handling, token analysis, the main vulnerability workflows and reporting. This last lesson pulls it together as a cheat sheet, a list of common mistakes, some practice scenarios to try on your own lab, and a longer self-test.

Remember the rule that runs through the whole track: test only what you own or are authorised to test. Screens and shortcuts below are labelled examples that can differ slightly between Burp versions.

Tool-by-tool cheat sheet

Tool Use it for Key habit
Proxy Intercept and inspect browser traffic; HTTP history Turn on scope-only logging; add comments and highlights
Target / Site map Build and review the map; set scope Set scope first; exclude logout and destructive paths
Repeater Resend one request with changes; compare responses Change one thing at a time; keep a control request
Intruder Send many variations of a request Small lists on authorised targets; throttle
Scanner Automated crawl and audit (Professional) Scope, configuration, then triage every result
Sequencer Test the randomness of tokens Collect thousands of samples
Decoder Encode and decode Base64, URL, HTML, hex, hashes Chain transformations
Comparer Diff two responses or files Find subtle differences for enumeration
Collaborator Detect out-of-band interactions Use unique payloads; never include real data
Logger Record all requests from all tools Search and filter evidence
Extensions Add tools (BApp Store) Review code and permissions first
Inspector View and edit decoded request parts Handy for cookies, JWTs, JSON

Useful shortcuts (Windows/Linux; use Cmd for Ctrl on macOS)

Action Shortcut
Send selected request to Repeater Ctrl+R
Send to Intruder Ctrl+I
Forward intercepted request Ctrl+F
Toggle intercept Ctrl+T
Send request in Repeater Ctrl+Space
Switch to the next tool tab Ctrl+Shift+Tab / Ctrl+Tab in many layouts
URL-encode selection Ctrl+U
URL-decode selection Ctrl+Shift+U
Base64-encode / decode selection Ctrl+B / Ctrl+Shift+B
Search in a message Ctrl+F in the editor

Check Burp, Settings, Hotkeys for the list in your version: shortcuts change, and you can rebind them.

Vulnerability testing checklist

  1. Scope and accounts ready; project saved.
  2. Map: browse, crawl, content discovery; list roles and workflows.
  3. Headers, cookies, JS: passive findings reviewed.
  4. Authentication: enumeration, lockout, password policy, reset, MFA, logout.
  5. Sessions: token randomness, fixation, expiry, JWT claims.
  6. Authorisation: role matrix, IDOR, method and path variations, mass assignment.
  7. Input: SQLi, XSS, SSRF and OAST, path traversal, command and template injection, XML, uploads.
  8. Logic: step skipping, price and quantity tampering, race conditions.
  9. Config: CORS, CSRF, error messages, debug features.
  10. Scan, triage, report, re-test.

Common mistakes

  • Testing before agreeing scope, or letting background traffic leak into the history.
  • Trusting the scanner: reporting tentative findings unverified.
  • Changing several things at once in Repeater, so you cannot say what caused a change.
  • Forgetting to exclude logout or reset URLs from a crawl.
  • Running Intruder with huge lists on a live system, causing lockouts or outages.
  • Not saving the project, then losing history when Burp closes.
  • Leaking evidence: unredacted tokens in screenshots, reports sent over plain email.
  • Ignoring the logic layer, where many critical bugs live.
  • Rating by label instead of real impact and context.
  • Stopping at "Burp found nothing": absence of scanner findings is not absence of vulnerabilities.

Practice scenarios

Try each on your own lab, writing a finding or a "tested, not vulnerable" note for it.

  1. Enumeration: compare login responses for an existing and a non-existing user with Repeater and Comparer. What differs (body, length, timing)?
  2. Token quality: capture 500 session tokens and run Sequencer. Are any positions fixed?
  3. Horizontal access: with two accounts, replay an order-view request using the other account's cookie.
  4. Reflection: find all places where a search term is reflected, and list the contexts.
  5. Parameter pairing: for a numeric ID, compare id=7 with id=8-1 and report what you learn about how the value is used.
  6. CORS probe: send an Origin header and read the response headers.
  7. Session handling: record a login macro and keep a Scanner task logged in across an expiry.
  8. Report: take your three best findings and write each in the standard structure with a CVSS vector.

Quick vector practice

This stand-in turns vector strings into readable text, useful for checking your own report entries. It decodes the CVSS 3.1 metrics you have used in the report lesson.

Python Decode a CVSS 3.1 vector string (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A tiny status-code triage helper

During testing you compare response codes constantly. This helper explains what a code usually means for access-control and login tests.

Python What does this status mean for my test? (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Where to go next

  • Keep practising on PortSwigger's free Web Security Academy labs and OWASP's vulnerable apps.
  • Read the OWASP Web Security Testing Guide and the OWASP Top 10, and learn how developers fix each issue; see also the Burp Suite track for the earlier chapters.
  • Learn a scripting language to automate your repetitive work, as you did in these projects.
  • Learn the defender's side: secure coding, logging and monitoring.
  • Pursue formal learning and certifications when you are ready, always with a strong ethical foundation.

Final self-test

Quick check ยท 7 questions

of 7 answered You scored / 7 ยท perfect!

  1. 1. What is the first thing to establish before any test against a real system?

    Authorisation and scope make the test legal and bounded.
  2. 2. A Repeater request with another user's cookie returns the first user's data. What is the finding?

    The server returned data without checking ownership.
  3. 3. Which tool measures token randomness?

    Sequencer analyses entropy in token samples.
  4. 4. Which tool would detect a blind SSRF through a DNS lookup?

    Collaborator records out-of-band interactions.
  5. 5. What is the best response to a Tentative scanner finding?

    Tentative results are leads that need manual confirmation.
  6. 6. Which CVSS band is a 9.8 score?

    9.0 to 10.0 is Critical.
  7. 7. What is the best protection for exported evidence?

    Evidence contains sensitive traffic and must be handled as such.

Summary

  • Know each tool's purpose and keep good habits: scope first, one change at a time, save the project.
  • Follow the checklist from setup through reporting and re-test.
  • Avoid common mistakes: unverified scanner results, leaking evidence, ignoring logic flaws.
  • Practise on your own lab and PortSwigger's free labs; keep learning the defender's side.
  • Authorised, ethical testing is what turns Burp skills into a career.

Next: back to the Burp Suite track page