7 Hidden Burp Suite Features That Save Hours of Manual Testing (2026)

Source: Dev.to

You’ve been using Burp Suite for a year. You know Proxy, Repeater, and Intruder and feel reasonably competent. Then you watch a senior bug bounty hunter do a session review and see requests filtering themselves based on response content, headers injecting automatically into every request, and a login macro re‑authenticating silently in the background while Intruder runs overnight.

That gap between “knows Burb” and “uses Burp at full capacity” is exactly where most hunters stay permanently. Nobody teaches the hidden features that experienced testers use every session. The tutorials cover the three obvious tabs and stop. The rest gets learned by accident—or not at all.

Below are the two hidden features that are fully supported in the Community Edition and can cut hours from every assessment.

Feature 1 — Burp Macros: Automated Re‑Authentication

The problem macros solve
When you run an Intruder attack against an authenticated endpoint, the session may expire after a while. Intruder keeps firing requests, but they now hit the login redirect, wasting time while reporting 302 responses as “success.”

How macros help
Macros record a login sequence and replay it automatically when Burp detects session expiry. Once set up, you never have to babysit a session again, making overnight Intruder runs viable.

Setup Walkthrough

Project Options → Sessions → Macros → Add
Sessions → Session Handling Rules → Add
Open Macro Editor → Test macro → verify login response = 200
Macro Editor → Configure item → Cookie/Parameter handling

The macro updates the session cookie from the login response and passes it to subsequent requests, ensuring authenticated testing continues without interruption regardless of how short the session timeout is.

---

Feature 2 — Logger++: Traffic You’re Currently Missing

Why Proxy History isn’t enough
Proxy History only shows requests that pass through Burp’s proxy listener. Logger++ captures everything Burp processes—including requests from extensions, the Scanner, Intruder payloads, and any tool using Burp’s upstream proxy.

What Logger++ adds

• Captures background traffic generated by extensions.
• Advanced filter bar lets you search across all captured traffic with regex, response keyword matching, and status‑code conditions simultaneously.
• Exportable logs for further analysis.

Setup and Advanced Filters

Extender → BApp Store → search “Logger++” → Install

Example filter expressions

Response.status == 200 && Response.body contains "password"
Request.headers contains "application/x-www-form-urlencoded"
Response.body.length > 50000

Exporting results

Logger++ → Log Table → right‑click → Export as CSV

During a complex assessment using multiple extensions, Logger++ often shows 3–5× more requests than Proxy History alone, making it possible to locate a specific response in a 100,000‑request capture within seconds.

---

For the full article with deeper technical detail, screenshots, code samples, and an interactive lab walk‑through, visit the original post on SecurityElites:

securityelites.com