ENTERPRISE
Managing scanning resources
-
Last updated: July 3, 2023
-
Read time: 2 Minutes
In Burp Suite Enterprise Edition, the term "scanning resources" refers to the systems that your scans run on. The type of scanning resource available to you depends on your deployment type.
Standard deployments
Standard deployments 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 container platform.
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 that the Enterprise Server is installed on. 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 deployment.
Kubernetes deployments
Kubernetes deployments 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 deployments run scans on a scalable 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 container platform.