Tools and labs

Burp Suite Intro for Beginners: Learn Web Security on Practice Sites Only

Burp Suite is the standard toolkit for testing web applications. It lets you see and change the requests your browser sends. Here is how to start with the free edition, on practice sites built to be tested.

Burp Suiteweb securityJuice ShopOWASP

What Burp Suite does

Burp is an intercepting proxy. Normally, your browser talks directly to a website. With Burp, the browser sends traffic through Burp first, so you can:

  • See every request and response in full.
  • Pause a request, change it, then send it on.
  • Resend requests with small changes to see how the server reacts.

This shows you what the website trusts from the browser, which is where many vulnerabilities live.

Setting up the free edition

  1. Download Burp Suite Community Edition from PortSwigger's official site.
  2. Start a temporary project with default settings.
  3. Go to the Proxy tab and click Open browser. Burp's built in Chromium browser is already configured to use the proxy and trust Burp's certificate, which saves setup time.
  4. Visit your practice target, for example your Juice Shop VM's address.
  5. Look at Proxy, HTTP history. Every request you made is listed.

Intercept: pause and inspect

Turn Intercept on in the Proxy tab. Now click something in the practice site. The request freezes in Burp. You can read the method (GET or POST), the path, headers like Cookie, and the body. Click Forward to send it, or edit a value first. Turn Intercept off when you just want to browse and record.

Exercise on Juice Shop: add an item to the basket and look at the request. Which values are sent? Which ones could a user change? This is how you start thinking like a tester.

Repeater: change and resend

Right click any request in HTTP history and choose Send to Repeater. In the Repeater tab, you can edit and resend the same request as many times as you want and compare responses. This is where much of manual testing happens: changing an ID, removing a parameter, or sending unexpected input to see how the application behaves.

What to look for: OWASP Top 10

The OWASP Top 10 lists the most critical web application security risk categories, such as broken access control, injection and security misconfiguration. Use it as your learning map. The Web Security Academy has free guided labs for topics like SQL injection, cross site scripting, access control and authentication. Do them in order, starting with apprentice level.

Community vs Professional edition

The Community Edition is free and includes the proxy, HTTP history, Repeater and a limited version of Intruder, enough for learning. The paid Professional edition adds features like an automated scanner. You do not need it as a beginner.

Turn practice into portfolio

For each lab you solve, write a short note: the vulnerability, how you found it with Burp, the request you changed, and how a developer should fix it. The "how to fix" part is what makes you valuable to teams, and it shows recruiters you understand both attack and defence. Add these notes to your GitHub portfolio.

Frequently asked questions

Do I need to know coding to use Burp? Basic understanding of HTTP and HTML is enough to start. JavaScript and a backend language help later when you analyse more complex applications.

Why does my browser show certificate errors with Burp? If you use your own browser, it needs to trust Burp's certificate. Using Burp's built in browser avoids this setup for beginners.

Can I use Burp on mobile apps? Yes, with extra setup, but start with web applications in your lab first.

Educational content, not legal advice. Check official sources before you rely on it. If you have lost money, call 1930 now. Terms