![]() If you have any questions about your licensing requirements, please contact our customer support team. This also applies to test, development, and staging environments. However, if you want to deploy Burp Suite Enterprise Edition in multiple environments, you must purchase a separate license for each environment. It doesn't matter how many scanning machines you deploy, or how many scans you run. If you are not able to connect to the public internet from your machine, then you need to configure an HTTP proxy.įor a single deployment of Burp Suite Enterprise Edition, you only need one license. In order to activate your license, the Enterprise server must be able to connect to on port 443. Activating your license after migrationīefore you activate, please be aware of the following requirements:.Migrating from a legacy cloud deployment.Deploying Burp Suite Enterprise Edition to Kubernetes.Integrating with issue tracking platforms.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. ![]()
0 Comments
Leave a Reply. |