If you have any questions about your licensing requirements, please contact our customer support team. Data is not shared between servers, and each is a separate deployment. If you want to deploy additional Burp Suite Enterprise Edition servers (for example, for testing in staging or development), you must purchase a separate license for each. Dedicated scanning machines connected to this single Enterprise server do not require their own license.

If you are not able to connect to the public internet from your machine, then you may need to configure an HTTP proxy.Ī single deployment of Burp Suite Enterprise Edition features a single server instance, and you only need one license. Refer to Configuring your environment network and firewall settings. In order to activate your license, the Enterprise server must be able to connect to on port 443.

Integrating with issue tracking platformsīefore you activate, please be aware of the following requirements:.

Configuring a Burp Scan using the generic CI/CD driver.

Configuring a site-driven scan using the generic CI/CD driver.

Configuring a site-driven scan in TeamCity.

Configuring a site-driven scan in Jenkins.

Creating an API user for CI/CD integration.

Environment network and firewall settings.

Configuring site and scan data settings.

Configuring default false positive settings.

Defining the scan configuration for a folder.

Defining the scan configuration for a site.

Step 4: Back up your data and stop your old service.

Step 1: Set up a suitable Kubernetes cluster.

Step 1: Prerequisites for the installation.

Preparing to deploy Burp Suite Enterprise Edition.

Burp suite pro license key