Enterprise Edition
Managing scanning resources for a self-hosted instance
-
Last updated: July 16, 2024
-
Read time: 2 Minutes
This section explains how to manage your scanning resources if you have a self-hosted instance of Burp Suite Enterprise Edition. It includes information for standard instances, and Kubernetes instances.
Standard instances
Standard instances of Burp Suite Enterprise Edition use either or both of the following resources:
- Scanning machines. These are dedicated physical or virtual machines that run scans. You can deploy as many scanning machines as you choose, and organize them into scanning pools for ease of management.
- CI-driven scans. You can run scans in your CI/CD pipeline, from temporary scanning resources that are created in a Docker container on a CI/CD agent node.
Scanning machines
- What is a scanning machine?
- Deploying additional scanning machines
- Managing scanning pools
- Assigning scan limits
Note
You can also deploy all of Burp Suite Enterprise Edition's components on a single machine, meaning that scans run on the same machine as the Enterprise server. While this is suitable for evaluation purposes, we do not recommend this setup in most production environments. For more information, see Single vs multi-machine architecture.
Kubernetes instances
Kubernetes instances of Burp Suite Enterprise Edition can use either or both of the following scanning resources:
- Auto-scaling scanning resources. Rather than requiring you to configure individual scanning machines, Kubernetes instances run scans using an auto-scaling resource pool. Burp Suite Enterprise Edition automatically creates scanning resources to cope with the number of concurrent scans that you need to run at any given time. The resources scale back down once they are no longer needed.
- CI-driven scans. You can run scans in your CI/CD pipeline, from temporary scanning resources that are created in a Docker container on a CI/CD agent node.