Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Burp Suite?

Burp Suite is an intercepting proxy and testing platform for web applications and APIs, letting a tester observe, modify, and replay every request a client sends.

Illustration for the cybersecurity term Burp Suite
Home / Blog / Cybersecurity Terms / What Is Burp Suite?
17 November 2026

What Is Burp Suite?

What Is Burp Suite?

Burp Suite is the tool most web application testing is actually done in. Built by PortSwigger, it works as an intercepting proxy: the browser or mobile application is configured to route traffic through it, Burp presents its own certificate so that encrypted traffic can be read, and every request becomes something the tester can pause, read, edit, and resend.

That one capability is what the discipline rests on. Client-side validation becomes irrelevant when the client is under the tester’s control, hidden form fields become editable, and a parameter the interface never shows becomes something you can supply.

The Tools Inside It

Editions and What They Change

EditionWhat it includesTypical user
CommunityProxy, Repeater, and a throttled Intruder; no scanner, no Collaborator, no saved projectsLearning and occasional manual work
ProfessionalFull scanner, Collaborator, unthrottled Intruder, project files, extensionsPenetration testers and application security engineers
EnterpriseScheduled scanning across many sites, CI integration, multi-user reportingContinuous scanning programmes

The Community edition’s throttling is deliberate and significant: Intruder runs at a crawl, which makes any real enumeration work impractical. For content discovery at speed, testers usually reach for ffuf instead and bring the interesting results back into Burp.

What the Scanner Does and Does Not Find

Burp’s scanner is good at the classes of defect that have a detectable signal: SQL injection including time-based and out-of-band variants, cross-site scripting in most contexts, server-side template injection, path traversal, insecure deserialisation patterns, missing security headers, and a long list of known misconfigurations. For those, it is more thorough than a human working by hand.

It does not find business logic flaws, because it has no idea what the business logic is supposed to be. It cannot tell that a discount code should not be applicable twice, that a workflow step was skipped, or that one user can read another’s records, since judging that requires knowing who should see what. Broken access control is the most common serious finding in web applications and the one least amenable to automation. A report produced only from scanner output is a hygiene check, not a penetration test.

Practical Points for Teams Being Tested

Two things make a difference to the depth of coverage you get. First, give the tester accounts that let authorisation be tested: at least two users per role, in separate tenants where the application is multi-tenant. Second, decide in advance what happens with your web application firewall. Leaving it fully enabled tests the firewall; allowlisting the tester’s source address tests the application. Most organisations want both, which means running part of the engagement each way and saying so in the report.

Where a mobile application is in scope, traffic has to be routed through Burp as well, which usually means installing the certificate into the device’s trusted store and defeating pinning with Objection or a Frida script.

At Privia Security, our Web Application Security Services combine manual testing in Burp with automated coverage, and report the two separately so you can see which findings came from where.

FAQ – Frequently Asked Questions

Is the Free Version of Burp Suite Enough?

For learning and for occasional manual inspection, yes. The proxy and Repeater are fully functional, and most manual testing happens in those two tools. Community edition has no scanner, no Collaborator for blind vulnerability detection, no saved projects, and a heavily throttled Intruder, so professional engagement work is impractical without the Professional licence.

Why Does Burp Need to Install a Certificate?

To read encrypted traffic it has to terminate the TLS connection, which means presenting a certificate the browser will accept. Burp generates its own certificate authority and the tester installs it in the browser’s trust store. It should only ever be installed on a dedicated testing machine or profile, because anything holding that authority can intercept all of the browser’s encrypted traffic.

Can Burp Test APIs and Mobile Applications?

Yes. APIs are tested by importing an OpenAPI definition or by proxying client traffic, with extensions adding GraphQL and JWT support. Mobile applications are tested by routing device traffic through Burp, which requires installing the certificate into the device trust store and, for applications using certificate pinning, bypassing the pinning check with Frida or Objection on a rooted or jailbroken test device.

Will Burp’s Scanner Replace a Manual Test?

No, and the gap is specific. The scanner reliably finds injection, cross-site scripting, template injection, path traversal, and missing headers. It cannot find business logic flaws or broken access control, because deciding that a response is wrong requires knowing what the application is supposed to permit. Those are the most common serious findings, and they are found manually.

Related Terms

You May Be Interested In These

What Is the ACME Protocol?

Cybersecurity Terms

17 November 2026

What Is the ACME Protocol?

Read More
What Is the Volatility Framework?

Cybersecurity Terms

17 November 2026

What Is the Volatility Framework?

Read More