Burp Suite Documentation
Burp Suite is an integrated platform for performing security testing of web applications. It is designed to support the methodology of a hands-on tester, and gives you complete control over the actions that it performs, and deep analysis of the results. Burp contains several tools that work together to carry out virtually any task you will encounter in your testing. It can automate all kinds of tasks in customizable ways, and lets you combine manual and automated techniques to make your testing faster, more reliable and more fun.
Note: Like any security testing software, Burp Suite contains functionality that can damage target systems. Testing for security flaws inherently involves interacting with targets in non-standard ways that can cause problems in some vulnerable targets. You should take due care when using Burp, read all documentation before use, back up target systems before testing, and not use Burp against any systems for which you are not authorized by the system owner, or for which the risk of damage is not accepted by you and the system owner.
Use the links below for help about Burp Suite:
- Getting started
- Start here if you are new to Burp or want to cover the key basics.
- Using Burp Suite
- This contains a detailed overview of Burp's user-driven testing
workflow, and how the tools work together.
- Burp tools -
This contains detailed documentation about each of Burp's individual
- Suite functions
- This describes all of the shared Suite-wide functions that support the
- Suite options - This
describes the Suite-wide options that affect the behavior of all tools.
- Extensibility - This
explains Burp's extensibility framework, and how you can extend Burp's
functionality with your own code.
- This contains tips for dealing with some common problems.
- Full documentation contents - A
structured site map of all the documentation.
Thursday, March 12, 2015
This release contains various bugfixes and minor enhancements, including:
- In the site map table, the "Method" column previously always showed GET for requests without a body, and POST for requests with a body, even if the actual method was different. This bug has now been fixed and the table shows the correct method.
- A bug which prevented client SSL certificates from being used when an upstream proxy is configured has been fixed.
- A bug which caused Decoder to fail to decode hex number HTML entities containing an upper-case X has been fixed.
See all release notes ›