Setting Up Your Testing Environment
Bug Bounty Fundamentals · Bug Bounty track
6 min read
In this module
Building Your Bug Hunting Workstation
Before you start testing, set up your environment properly. A well-configured workstation is the difference between methodical research and a folder full of screenshots you can't tell apart a week later. This lesson covers the tools, browser settings, note-taking habits, and operational security every bug bounty researcher should have wired up before their first session.
Burp Suite: Your Primary Tool
Burp Suite is the industry-standard intercepting proxy for web testing. It sits between your browser and the target server so you can inspect, modify, and replay every HTTP and HTTPS request that passes through.
The free Community Edition gives you the core proxy, repeater, decoder, and a rate-limited Intruder. The Professional Edition adds an automated scanner, full-speed Intruder, and content discovery. Most serious researchers run Pro.
Setting up Burp Suite:
- Download and install Burp Suite from PortSwigger's website
- Start Burp and navigate to the Proxy tab
- Configure the proxy listener (default:
127.0.0.1:8080) - Export and install Burp's CA certificate in your testing browser
Burp Suite Proxy Configuration: Listener: 127.0.0.1:8080 Intercept: Off by default (turn on when needed) HTTP history: Records all proxied traffic Target scope: Configure to filter only in-scope domainsOWASP ZAP is a free, open-source alternative. Similar intercepting proxy functionality, no licence fee, perfectly fine if you'd rather not invest in Burp on day one.
Browser Configuration
Use a dedicated browser profile for testing. Never your personal one. Keeping them apart stops your personal cookies, saved passwords, and browsing history from leaking into your testing — or worse, surfacing in a screenshot.
Configure the testing profile:
- Set the HTTP proxy to Burp Suite's listener address (
127.0.0.1:8080) - Install Burp's CA certificate to avoid TLS errors
- Install useful extensions: FoxyProxy (for quick proxy switching), Wappalyzer (technology fingerprinting), and a cookie editor
- Disable caching to ensure you see fresh responses
- Consider using Firefox for testing, as its proxy settings are independent of the system proxy
Keep your testing browser completely separate from your personal browsing. If you test while logged into personal accounts, you risk accidentally submitting reports with personal cookies, exposing personal data in screenshots, or having your testing traffic mixed with personal traffic in Burp's history. A dedicated browser profile or a separate browser application eliminates these risks.
Note-Taking and Documentation
Documentation matters as much as the testing. Every finding, every odd behaviour, every rabbit hole you fall down — write it down. Three weeks into a programme, when you finally trip over a vulnerability, you'll need to retrace your steps to write a clear report. Past-you owes future-you that paper trail.
Effective documentation includes:
- Target notes: subdomains discovered, technologies identified, interesting endpoints found during reconnaissance
- Testing log: what you tested, what you tried, what the results were
- Screenshots and recordings: visual evidence of every finding at the time of discovery
- Request/response pairs: exported from Burp Suite for reproducibility
Tools commonly used for documentation:
Note-taking: Obsidian, Notion, or plain Markdown filesScreenshots: Flameshot, ShareX, or built-in OS toolsScreen recording: OBS Studio for video proof of conceptsOrganisation: One directory per programme, subdirectories per targetSettle on a naming convention early and stick with it. After a few months of testing across multiple programmes, your folder structure is the only thing keeping you sane.
VPN and Operational Security
Your IP address is visible to every target you hit. Use a VPN to keep your testing traffic separate from your personal browsing. You get privacy, and you avoid awkward conversations with your ISP about why your home connection is suddenly probing a Fortune 500's perimeter.
Key operational security practices:
- Use a commercial VPN or a dedicated VPS for testing traffic
- Never test from your employer's network without explicit permission
- Use separate email addresses for platform accounts and personal use
- Be cautious with screenshots - review them for personal information before including in reports
- Secure your testing notes - they may contain sensitive details about vulnerabilities in production systems
A VPN separates your traffic from your personal life, but it shouldn't hide you from the programme. Many programmes ask you to identify your testing traffic, for example with a custom request header carrying your username, or to sign up test accounts with your platform alias email. Some also ban VPN or shared exit addresses, or ask for a fixed source IP. Read the rules of engagement and set this up in Burp before you send the first request.
Organising Your Workflow
A structured workflow saves you from re-doing work you forgot you'd already done. Organise by programme, then by target:
~/bounties/ └── hackerone/ └── example-corp/ ├── recon/ │ ├── subdomains.txt │ ├── endpoints.txt │ └── technologies.md ├── findings/ │ ├── xss-search-page/ │ │ ├── notes.md │ │ ├── screenshot.png │ │ └── request.txt │ └── idor-api-v2/ │ ├── notes.md │ └── burp-export.xml └── reports/ └── submitted/Additional tools to integrate into your workflow:
- Postman for API testing and request crafting
- Nuclei for template-based vulnerability scanning (check programme rules before automated scanning)
- ffuf or gobuster for content discovery and directory brute-forcing
Before you point any of this at a live programme, practise on targets built to be attacked: PortSwigger's free Web Security Academy labs, OWASP Juice Shop and DVWA (which you run yourself) are all fair game.
Start simple. You don't need every tool on day one. Burp Suite and a well-configured browser will get you a long way; add the rest as your methodology grows into them. Just make sure your notes keep pace with your testing.