Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 38 ยท Projects and Practice

Project: Build a Practice Lab and Define Scope

Set up a safe local practice lab for Burp Suite, write a scope and rules-of-engagement document, and use a Python checker to keep tests inside the allowed targets.

The best way to learn Burp is to practise on targets that exist to be tested. In this project you build a local lab, write down the scope and rules of engagement, and create a small checker that stops you from accidentally testing something outside scope. These habits make you faster and, more importantly, keep you legal.

This is a project lesson: some steps happen on your own computer outside this page. Commands and screens are labelled examples; the runnable code is a Python stand-in.

Part 1: choose lab targets

Use applications designed for testing, run on your own machine or a private network:

  • Deliberately vulnerable web apps that you install locally, such as OWASP Juice Shop, DVWA (Damn Vulnerable Web Application), or WebGoat. They are free and often run in a container.
  • PortSwigger Web Security Academy: free labs hosted by PortSwigger that you are explicitly allowed to attack with Burp.
  • Your own small app written for the purpose: an easy way to understand both sides of a bug.

Never use a real company's website, your school's portal, or a friend's site "just to practise". Written permission is the line between security testing and a crime.

Example: run a vulnerable app in a container (labelled example)

Terminal
# Run on your own machine only; binds to localhost so nothing is exposed
docker run --rm -p 127.0.0.1:3000:3000 bkimminich/juice-shop
# then browse to http://127.0.0.1:3000 through Burp's proxy

Binding to 127.0.0.1 keeps the vulnerable application invisible to the rest of your network. A vulnerable app on a shared Wi-Fi network is a real risk to others.

Part 2: connect Burp to the lab

You met the proxy in the earlier chapters. A quick checklist for the lab:

  1. Burp Proxy listener on 127.0.0.1:8080.
  2. Use Burp's built-in browser (it is already configured and trusts Burp's certificate), or configure a separate browser profile with the proxy and install Burp's CA certificate.
  3. Browse the lab so the Target, Site map fills up.
  4. Set Target scope to the lab host only. In the Proxy settings, enable "don't send items to history that are out of scope".
  5. Save a project file named after the exercise.

Isolate the testing environment

  • Use a separate browser profile or the built-in browser, so your personal logins never pass through Burp.
  • Keep the lab on localhost or a host-only virtual network.
  • Take a snapshot or know how to reset the app (re-run the container) so a broken state is a minute's work.

Part 3: write the rules of engagement

Even for a lab, write the document you would need on a real job. It builds the habit, and one day you will need it for real.

Section Example entry for your lab
Objective Find and document web vulnerabilities in the training app
In-scope targets http://127.0.0.1:3000 (all paths)
Out of scope Everything else, including other ports and the internet
Allowed techniques Manual testing, Burp Scanner (light), Intruder with small lists
Forbidden Denial of service, attacks on other users' machines, data exfiltration beyond test data
Accounts tester1, tester2 created for the exercise
Rate limit At most 10 requests per second
Test window Any time (local lab)
Contacts Yourself, and a note of who to call if something breaks
Evidence handling Stored in the project folder; deleted when the course ends

For a real client, the signed authorisation letter lists every IP address and hostname, the dates, a named contact and an emergency stop procedure. Never start without it.

Part 4: a scope checker

Burp's scope settings are powerful but easy to misconfigure. This stand-in builds a tiny scope list and tests URLs against it, including the tricks that cause accidents: look-alike hostnames, other ports, and the wrong scheme. Run it, then change the lists to match your own lab.

Python Scope checker for your rules of engagement (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.

The checker shows why you compare scheme, host and port exactly, never with startswith on the whole URL: http://127.0.0.1.evil.example would sneak past a prefix test. Burp's own scope uses the same structured fields (protocol, host, port, file).

Practice: extend the checker

Add a rule for a second lab host, make the checker read URLs from a text file you export from Burp (the next project lesson parses a real export), and make it print a warning for every out-of-scope request found in your history. If you ever see one, you have found a flaw in your setup, not just a test URL.

In Burp, turn on Proxy, Settings, Intercept client requests, "And URL Is in target scope", so interception only stops on in-scope requests. It keeps unrelated browser background traffic out of your way.

Part 5: your first lab tasks

With the lab running, scoped and saved, do these warm-ups using only what earlier lessons covered:

  1. Browse every feature and note the number of locations in the site map.
  2. Run a passive crawl-and-audit and list the issue names found (Scanner basics).
  3. Register two accounts and write the role matrix for access control testing.
  4. Capture ten login tokens and run Sequencer.
  5. Save the project and note the time you spent in a testing log.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which targets are appropriate for practising Burp?

    Only systems you own or have written permission to test are legal targets.
  2. 2. Why bind a vulnerable app to 127.0.0.1?

    Localhost binding prevents others from reaching a deliberately weak application.
  3. 3. What belongs in rules of engagement?

    Clear scope and limits protect both tester and client.
  4. 4. Why compare scheme, host and port exactly in a scope check?

    Exact matching avoids prefix tricks and accidental out-of-scope testing.

Summary

  • Practise on vulnerable apps you run locally or on labs that explicitly allow testing.
  • Keep the lab on localhost, use a clean browser profile, and save a project file.
  • Write rules of engagement (scope, techniques, limits, accounts, contacts) even for a lab.
  • Use exact scheme, host and port matching to keep tests in scope.
  • Commands and screens here are labelled examples; the Python checker is a runnable stand-in.

Next: Project: a full assessment methodology