This tab contains settings for scheduled tasks, Burp Collaborator server, and logging.
See the Task Scheduler documentation.
Burp Collaborator is an external service that Burp can use to help discover many kinds of vulnerabilities. For more details about the functionality and alternative methods of utilization of Burp Collaborator, see the main Burp Collaborator documentation.
The functionality of Burp Collaborator gives rise to issues that require careful consideration by users. Users should ensure that they fully understand the functionality and the alternative methods of utilization of Burp Collaborator, and have considered the consequences of utilization for themselves and their organization.
The following options for using Burp Collaborator server are available:
We periodically add new domain names for the public Collaborator server to reduce the chance of WAF blacklisting resulting in false negatives. By default, the Burp Collaborator client and Burp Scanner always use the newest public Collaborator domain that was available when your current version of Burp Suite Professional or Burp Scanner was released. At the moment, this will either be burpcollaborator.net or oastify.net.
To ensure that you experience the full benefits of Burp Collaborator, please make sure that the machine running Burp Scanner or the Burp Collaborator client can access both of these domains on ports 80 and 443.
If you are using a private Collaborator server, you will need to configure Burp with the details of its location. The following options are available:
If you have configured your Collaborator Server to use non-standard ports, then you must specify them here.
The following further options are also available:
These settings control logging of HTTP requests and responses. Logging can be configured per-tool or for all Burp traffic.
Burp's browser is sandboxed by default. However, in a few very specific circumstances, such as when running in Linux as root, you might not be able to launch browser-powered scans using the sandbox.
If you run into issues, use the Health check for Burp's browser tool to see if this is the cause. If so, you can enable the option Allow the browser to run without a sandbox. Before doing this, please make sure that you are aware of the security implications. Scanning hostile websites without the sandbox increases the risk of your local system being compromised.
In certain environments, Burp's browser may repeatedly crash after attempting to use a GPU where none exists. If you experience this problem, select the Stop the Burp's browser using the GPU option.