Support
Support Center

Burp Community

See what our users are saying about Burp Suite:

How do I?

New Post View All

Feature Requests

New Post View All

Burp Extensions

New Post View All

Bug Reports

New Post View All
Documentation
Documentation

Burp Suite Documentation

Take a look at our Documentation section for full details about every Burp Suite tool, function and configuration option.

Burp Suite Professional and Community editions Burp Suite Enterprise Edition
Burp Scanner Burp Collaborator
Burp Infiltrator Full Documentation Contents
Extensibility
Extensibility

Burp Extender

Burp Extender lets you extend the functionality of Burp Suite in numerous ways.

Extensions can be written in Java, Python or Ruby.

API documentation Writing your first Burp Suite extension
Sample extensions View community discussions about Extensibility
  1. Support Center
  2. Documentation
  3. Desktop editions
  4. Dashboard
  5. Task execution settings

Task execution settings

Burp Suite lets you configure multiple automated tasks simultaneously. Executing a large volume of work in parallel is liable to cause problems, either in your own machine (by exhausting CPU, memory, or your network connection) or in the applications being tested. Burp helps to avoid this happening by managing the execution of tasks and the way in which resources are assigned to them.

The task execution settings can be accessed by clicking the gear icon at the top of the Tasks panel on the Burp Dashboard.

Task auto-start

You can individually pause and resume tasks in Burp's Dashboard. You can also configure whether to automatically start new tasks as they are created. The following options are available:

Resource pools

A resource pool is a grouping of tasks that share a quota of network resources. Each resource pool can be configured with its own throttling settings which control the number of requests that can be made concurrently, or the rate at which requests can be made, or both.

Each task is assigned to a resource pool when it is created, and tasks can be moved between resource pools at any time.

Using resource pools is particularly useful if you are testing different applications that tolerate automated requests at different rates. They are also useful to prioritize different areas of your testing. For example, you might create one task performing a full crawl and audit of an application, and let this run in the background with a small number of concurrent requests; you might create another task for auditing specific individual requests that you select, and let this run with a larger number of concurrent requests to give it priority.

back-to-top