This article provides a complete hands-on guide to installing, configuring, and using Burp Suite for web application security testing, specifically targeting beginners who want to move from theoretical knowledge to practical vulnerability discovery. The guide walks through setting up Burp's proxy interception with Firefox and CA certificate installation, then demonstrates core workflows including request modification, HTTP history analysis, and manual testing with Repeater. It matters because Burp Suite is the industry standard tool used by professional penetration testers and bug bounty hunters, and this guide closes the gap between knowing Burp exists and being able to use it to find real vulnerabilities.
- FoxyProxy enables efficient proxy togglingFoxyProxy is a Firefox extension that allows switching Burp proxy routing on and off with a single click, eliminating the need to manually reconfigure Firefox proxy settings each time testing starts or stops. The setup involves installing the extension, adding a configuration pointing to 127.0.0.1:8080, and then toggling between 'Burp Suite' and 'Disable FoxyProxy' modes. This workflow is presented as standard practice among professional testers.
- CA certificate installation enables HTTPS interceptionInstalling Burp's CA certificate in Firefox (accessed at http://burpsuite and imported into Firefox's certificate authorities) allows Burp to intercept and display encrypted HTTPS traffic rather than being blocked by security warnings. Without this step, Burp can only see HTTP traffic. The certificate must be marked as trusted for website identification in Firefox's security settings, after which HTTPS requests appear in Burp's Proxy tab without browser warnings.
- HTTP History maps the application attack surfaceWith Intercept OFF, browsing the target application with FoxyProxy active populates Burp's HTTP History tab with a complete record of every request. The article specifies what to look for during this mapping phase: POST requests for form submissions, numeric IDs in URLs for IDOR vectors, API endpoints like /api/ or /graphql/, redirects (302 responses), parameters reflecting in responses (XSS candidates), and authorization headers. Any interesting request can be right-clicked and sent to Repeater for manual testing.
- Repeater enables systematic manual request modificationRepeater displays the raw HTTP request on the left and server response on the right, allowing testers to modify any part of a request (parameters, headers, body, method) and immediately observe how the application responds. The article demonstrates this with an IDOR example where changing an id parameter from 2850 to 2849 returns another user's email and phone number, confirming the vulnerability. This is described as the core workflow where most testing time is spent.
- Intruder automates payload testing with four attack typesIntruder substitutes multiple payload values into marked request positions. Sniper (most used) cycles through one payload set across each marked position, suitable for fuzzing a single parameter or brute-forcing passwords. Pitchfork iterates multiple payload sets in parallel for username:password combinations. Cluster Bomb tests all combinations of multiple payload sets for credential stuffing. Battering Ram inserts the same value into all marked positions simultaneously. The Community Edition is rate-limited, so Intruder should be used for focused tests rather than large wordlists.
- Decoder & Comparer provide quick reference utilitiesDecoder performs on-the-fly encoding and decoding operations including URL encoding, Base64 decoding (useful for JWT tokens), HTML decoding, and hex encoding. Comparer allows side-by-side comparison of two responses by pasting them, which is critical for distinguishing true and false conditions in SQL injection testing or comparing different application states.
- IDOR testing workflow uses HTTP History and RepeaterThe demonstrated IDOR test on DVWA follows this sequence: log in with an authorised test account, browse to the profile page with Intercept OFF to populate HTTP History, locate the profile request in HTTP History, send it to Repeater, modify the user ID parameter to another account's ID, and observe whether the server returns that other account's data using only the original session cookie. If unauthorized data is returned, IDOR is confirmed, and both request and response should be documented.
- Community Edition provides sufficient foundational toolsBurp Suite Community Edition is free and includes Proxy, Repeater, Intruder (rate-limited), Decoder, Comparer, and basic scanner functionality. Professional Edition ($449/year) adds full automated scanning and unlimited Intruder capabilities. The article states that Community Edition is sufficient for most learning and bug bounty work.
Bottom line: Setting up Burp Suite correctly (FoxyProxy + CA certificate installation) takes approximately 20 minutes and establishes a reusable workflow for life: browse with Intercept OFF to map HTTP History, send interesting requests to Repeater for manual modification and testing, and use Intruder for automated payload fuzzing—this systematic methodology is how professional penetration testers and bug bounty hunters discover real vulnerabilities.
Burp Suite is the tool that separates people who have heard of web application security from people who actually do it. Every professional web application penetration tester has Burp open. Every serious bug bounty hunter has Burp configured. The gap between “I’ve heard of Burp Suite” and “I can use Burp Suite to find real vulnerabilities” is a one-time setup and a few hours of hands-on practice. Lets learn How to Use Burp Suite for Beginners from very scratch.
This guide gives you that setup and that practice — completely step by step. By the end, you will have Burp Suite installed and properly configured, you will have intercepted your first HTTPS request, modified it, and sent it to Repeater. Then you will use that workflow to demonstrate a simple IDOR finding on DVWA. Everything practical, everything on your own authorised lab.
Step 1 — Install & Launch Burp Suite
On Kali Linux, Burp Suite Community is pre-installed. Launch it from the terminal or the Applications > Web Application Analysis menu. On other systems, download from portswigger.net/burp/communitydownload — free, no account required.
burpsuite &
# Or from Applications > Web Application Analysis > burpsuite
# On first launch: Temporary project > Use Burp defaults > Start Burp
Also see our Burp Suite Beginner Guide and Burp Suite Cheat Sheet for quick-reference commands.
Step 2 — Configure FoxyProxy in Firefox
FoxyProxy is a Firefox extension that lets you switch proxy settings with one click. Without it, you would have to manually change Firefox proxy settings every time you start or stop testing. This is the fastest and cleanest workflow.
Step 3 — Install Burp’s CA Certificate (HTTPS Interception)
Without the CA certificate, Firefox blocks HTTPS traffic with security warnings and Burp cannot see encrypted content. This is the step most beginners miss — and why they think Burp only works on HTTP. The certificate tells Firefox to trust Burp as an intermediate certificate authority.
Proxy — Intercept, Modify & Forward
Burp Suite Community Edition
HTTP History — Map the Application’s Attack Surface
With Intercept OFF, browse every page of the target application while FoxyProxy routes traffic through Burp. Click every button. Submit every form. Use every feature. Burp’s HTTP History tab records every single request — this becomes your attack surface map.
Repeater — The Heart of Manual Testing
Repeater is where you spend most of your testing time. It shows the raw HTTP request on the left and the server’s raw response on the right. Modify any part of the request — parameters, headers, body, method — and click Send to see exactly how the application responds to each change.
Intruder — Automated Payload Testing
Intruder automates sending many request variations by substituting payload values into marked positions. In Community Edition it is rate-limited — use it for focused tests, not large wordlists. Four attack types:
Decoder & Comparer — Quick Reference
URL encode: admin+password → admin%2Bpassword
Base64 decode: eyJhbGciOiJ… → {“alg”:”HS256″,”typ”:”JWT”}
HTML decode: <script> → <script>
Hex encode: A → 41
# Tip — Decode JWT tokens in Decoder to check algorithm and claims
# Comparer — paste two responses to diff them side-by-side
# Critical for: comparing responses to true/false SQLi conditions
Your First IDOR Test Using Burp Suite — On DVWA
This is the complete IDOR workflow using Burp Suite — the same methodology used in real authorised bug bounty testing. On DVWA with two test accounts:
id=1 to id=2 (Account B’s ID). Click Send.Frequently Asked Questions – How to use Burp Suite for Beginners
The Burp Suite setup in this guide — FoxyProxy, CA certificate, HTTP History, Repeater — takes about 20 minutes to complete and then you use it for the rest of your security career. Every serious web application tester I know has this exact setup. The tool is not magic; it just makes every request and response visible and modifiable. Everything interesting you find in web application testing, you find through this lens.

