Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 38 ยท Getting Started

What Is Burp Suite?

Learn what Burp Suite is, why testers sit it between a browser and a web app, and what the intercepting proxy idea lets you see, change and replay.

Burp Suite is a toolkit for testing the security of web applications. Its core idea is simple: instead of letting your browser talk straight to a website, you put a small program in the middle. Every request the browser sends, and every response the server returns, passes through that program, where you can read it, pause it, change it and send it again.

That middle program is called an intercepting proxy, and it is the reason Burp exists. Browsers hide most of what happens on the wire. A form looks like three boxes and a button, but underneath it is a structured message with headers, cookies, hidden fields and tokens. Burp shows you that message exactly as the server sees it, which is where most web security flaws live.

Burp Suite is a professional testing tool. Use it only on systems you own or have written permission to test. The next lesson, Legal and ethical testing, explains what that means in practice. Everything in this track is written for authorised, defensive work.

In this track the real Burp Suite is shown through realistic, labelled example screens and output. It is a desktop application, so it cannot run inside this website. The runnable code blocks are small Python stand-ins that model one idea at a time (a proxy queue, a scope rule, a crawler against a fake in-memory site), so you can experiment with the logic safely. Whenever a block is a stand-in, it says so.

The problem Burp solves

When you use a website normally, the browser decides what to send. It only sends what the page's HTML and JavaScript allow: a price field might be read-only, a dropdown might offer three choices, a button might be hidden for non-admin users. Those are client-side controls. A security tester needs to know whether the server enforces the same rules, because anyone can send a hand-made request that skips the browser's interface.

A proxy gives you the missing view. With it you can ask real questions:

  • Does the server accept a price I changed to 0.01?
  • What happens if I request /orders/1002 while logged in as the owner of order 1001?
  • Does the session cookie get the Secure and HttpOnly flags?
  • Which parameters does the page quietly send that I never saw in the form?
flowchart LR
  B["Browser"] -->|"1. request"| P["Burp proxy<br/>127.0.0.1:8080"]
  P -->|"2. forwarded<br/>(maybe edited)"| S["Web server"]
  S -->|"3. response"| P
  P -->|"4. delivered<br/>(maybe edited)"| B
  P -.->|"copy of every message"| H["HTTP history"]

The proxy sits on the path in both directions and keeps a copy of everything.

What "suite" means

Burp is not a single feature. It is a set of cooperating tools that all share the same data. You capture traffic in the Proxy, map the application in the Target tab, replay and edit single requests in Repeater, automate variations in Intruder, decode odd values in Decoder, compare two responses in Comparer, and (in paid editions) find issues automatically with the Scanner. A request found in one tool can be sent to any other with a right-click, which is what makes the workflow fast.

You will meet each tool in its own lesson. The tools tour gives a map first.

A request as Burp shows it

Here is a raw HTTP request, the way Burp's Raw view displays it. This one is a made-up login against a made-up lab address:

HTTP
POST /login HTTP/1.1
Host: shop.lab.test
Cookie: session=abc123
Content-Type: application/x-www-form-urlencoded
Content-Length: 31

username=alice&password=wonder

Every part is plain text: a request line (method, path, version), headers, a blank line, then the body. Learning to read this fluently is the most useful early skill, and HTTP for Burp users covers it in depth.

Try it: a toy intercepting proxy

This is a stand-in, not Burp. It models what the proxy does in the simplest possible way: it receives a request from a "browser" function, lets a "tester" function optionally change it, forwards it to a fake server function, and records the exchange in a history list. No network is involved.

Python Stand-in: a tiny intercepting proxy

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 second request shows why testers care: a negative quantity produces a negative total, a classic business-logic flaw that the browser's form would never have let you submit. The proxy did not create the bug; it only made it visible.

What Burp is not

Burp is not an "auto-hack" button. It does not know your application's business rules, and automated findings still need a human to confirm them. It also is not an antivirus, a firewall or a network scanner: it focuses on HTTP and HTTPS traffic between a client and a web application or API. For port scanning or operating-system issues, other tools apply.

Try it: reading the exchange

A second stand-in parses a raw request string into parts, the way Burp's Raw and Pretty views break a message into sections.

Python Stand-in: split a raw request into parts

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.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main job of an intercepting proxy such as Burp Suite?

    The proxy relays traffic in both directions while giving you a chance to inspect and edit each message, which exposes what the browser normally hides.
  2. 2. Why is changing a request in a proxy useful for security testing?

    Client-side limits such as read-only fields can be skipped by sending a hand-made request. The test is whether the server still rejects invalid input.
  3. 3. Which statement about the code blocks in this track is true?

    Burp is a desktop application, so the runnable blocks are small Python models and the real tool is shown with labelled example output.
  4. 4. Which of these is outside what Burp mainly does?

    Burp focuses on HTTP and HTTPS traffic between a client and a web application. Port scanning belongs to network tools.

Summary

  • Burp Suite is an intercepting proxy plus a set of tools for testing web application security.
  • It shows the exact messages the browser and server exchange, and lets you edit and replay them.
  • Server-side rules matter more than browser-side limits; a proxy lets you test the server directly.
  • The suite's tools share data: send a request from one tool to another with a right-click.
  • Use it only with permission, and treat automated findings as leads to confirm by hand.

Next: Legal and ethical testing