Skip to content

Intermediate · Web application testing: Burp Suite and the basics · topic 19 of 35 · 20 min

Burp Suite basics: the intercepting proxy

Explanation

Burp Suite sits between your browser and the web app as a proxy, so you can see and change every request before it reaches the server. Its Proxy, Repeater and Intruder tools are the core of web testing. The free Community edition is enough to learn.

What a proxy does

A proxy is a program that sits in the middle of a connection. Burp Suite is an intercepting proxy for web testing: you point your browser at Burp, and Burp sees every request on its way to the server and every response on its way back. You can read them, pause them, and change them before they continue.

Think of it like this: Think of Burp as a post office that opens every letter between you and the server, lets you read it, and lets you edit it before sending it on. For testing your own or authorised targets, that power is exactly what you need to see how the app behaves with unexpected input.

The main tools

ToolWhat it does
ProxyIntercept and view/edit requests and responses live
HTTP historyA log of every request that passed through
RepeaterResend a single request again and again, tweaking it each time
IntruderAutomate sending many variations of a request (rate-limited in Community)
Decoder / ComparerEncode/decode values; compare two responses

Repeater is where most learning happens: you capture a request, send it to Repeater, change one thing (an ID, a field, a header), resend, and watch how the response changes. That loop — change one thing, observe — is the heart of manual web testing.

Setting it up

You run Burp, set your browser (or Burp's built-in browser) to use Burp as its proxy, and install Burp's certificate so HTTPS can be read. The official docs walk through this. In your lab, point it at your DVWA or Juice Shop VM and start watching requests.

Careful: Burp lets you change requests to anything. Use it only against your own lab or an authorised, in-scope target. Intercepting traffic to a site you do not have permission to test is unauthorised access. Also be careful: the Community edition's Intruder is deliberately slowed, and heavy automation can disrupt a target.

Detection and defence

Detection: using a proxy is invisible to the server by itself, but the unusual requests a tester sends through it (odd values, repeated tries, scripts in fields) are what defenders log and alert on. Defence has nothing to do with the proxy and everything to do with the app: validate and sanitise all input, enforce access control on the server, and watch logs for abnormal requests. If the app is built safely, it does not matter that an attacker can see and change requests.

Tip: OWASP ZAP is a free, open-source alternative to Burp with similar features. Either is fine for learning. PortSwigger's Web Security Academy teaches Burp hands-on, for free.

Need help?

Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.

Try:

Watch the lesson

Burp Suite basics: the intercepting proxy · 1/7

Proxy = the middle

A proxy sits in the middle and sees every request and response.

Prefer a video by a teacher? Find free videos on “burp suite community edition tutorial proxy repeater beginners” on YouTube ↗

In real life: One changed number

In her lab, a learner logs into a web app and loads her profile: GET /profile?id=7. She sends that request to Burp Repeater, changes id=7 to id=8, and resends. The app returns another user's profile. She has found a broken access-control flaw (covered next module) using nothing but the proxy and one changed number. She records it with the fix: the server must check that the logged-in user owns the record it returns.

Practice (0/3 done)

Task 1 · Question

Burp Suite is…

Task 2 · Question

Which Burp tool resends one request with small changes each time?

Task 3 · Practice

Write step-by-step how you would use Burp Repeater in your lab to test whether changing an id in a request shows another user's data — and the fix you would recommend.

Quick quiz

Question 1

1.To read HTTPS traffic in Burp you must…

Question 2

2.A free, open-source alternative to Burp is…

Question 3

3.The real defence against proxy-based tampering is…

Question 4

4.You may use Burp against…

Read more (free)

Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.

To read HTTPS traffic in Burp you must…

Answer: Install Burp's certificate in the browser

Installing Burp's CA certificate lets it decrypt HTTPS for you.

A free, open-source alternative to Burp is…

Answer: OWASP ZAP

OWASP ZAP is a free alternative proxy.

The real defence against proxy-based tampering is…

Answer: Validating input and enforcing access control on the server

A safely built app does not care that requests can be changed.

You may use Burp against…

Answer: Only your lab or an authorised, in-scope target

Intercepting traffic requires authorisation.

To read a tool's manual you type…Related

Answer: man toolname

man toolname (or toolname --help) shows how a command works.

From Kali Linux: the attacker machine

Most web attacks work by…Related

Answer: Sending a request the developer did not expect

Unexpected input in a request is the core of web attacks.

From How web requests work (and why that matters)

What does HSTS tell the browser?Related

Answer: Use only HTTPS for this site in future

Strict-Transport-Security makes the browser refuse plain HTTP for the site.

From HTTP, HTTPS and TLS

The single most effective defence against a Metasploit exploit is…Related

Answer: Patching the vulnerability it targets

With no unpatched flaw, the matching exploit fails.

From Metasploit basics (in the lab)

Pass the quiz (60% or more) or mark this topic as done when you are ready.

Your progress is saved on this device only.

Next steps

  1. 1 more topic in “Web application testing: Burp Suite and the basics” before its exam: The OWASP approach to web testing.
  2. Module 6 exam: web testing and Burp · 12 questions · 20 min, without help. 3 topics of this module still to finish first.
  3. Then the next module, Web attacks and their fixes. 35 topics left in the course before the final exam.

← Previous: How web requests work (and why that matters)