ENTERPRISE

Burp Suite Enterprise Edition system requirements

• Last updated: August 9, 2022

• Read time: 4 Minutes

The system requirements for machines running a standard deployment of Burp Suite Enterprise Edition depend on a variety of factors, including:

• The number of concurrent scans you want to run
• The nature and scope of the application being scanned
• The number of machines you want to use. You can either run all of Burp Suite Enterprise Edition's components on a single machine or use a multi-machine deployment.
• The number of issues reported.
• The number of active Burp Suite Enterprise Edition users.

As a result, the system requirements listed in this section are general recommendations that should provide satisfactory performance for most use cases. When provisioning machines, please be aware that you might need to upgrade them later depending on your actual usage.

General requirements

The following requirements apply to all standard deployments of Burp Suite Enterprise Edition:

• All machines on which Burp Suite Enterprise Edition components are installed must have a 64-bit architecture.
• The disk location (configured during the installation process) must reside on locally attached storage rather than a network file system. Please note that the free space required is not only for the up-front installation. Disk space is used for storage of ephemeral data during scans and product updates.

Be aware that to get the most out of Burp Suite Enterprise Edition, each of your machines will likely need to run multiple concurrent scans. In many cases, this will require you to use a dedicated server or server-class virtual machine in order to meet the system requirements.

Swap space (Linux only)

If you want to deploy Burp Suite Enterprise Edition to a Linux-based machine, you should allocate sufficient storage as swap space. This can help to improve the stability of scans by providing a fallback for occasions when your scans are using large amounts of memory.

We recommend allocating the same amount of memory as the available RAM, plus an additional 2 GB. For example, for a machine with 32 GB RAM, you should create a 34 GB swap file.

If you deploy Burp Suite Enterprise Edition on a cloud-based virtual machine, such as an EC2 instance on AWS, you may need to create a suitable swap file manually. For details on how to do this, please consult your cloud service provider's documentation. When deploying on a local machine, sufficient swap space is likely already available.

System requirements for single-machine deployment

If you want to run scans on the same machine as your Enterprise server, then the following requirements apply.

	Free disk space	RAM	CPU cores
Base installation	10 GB	16 GB	4
Per concurrent scan	+ 20 GB	+ 8 GB	+ 4
Total for 1 scan	30 GB	24 GB	8
Total for 2 concurrent scans	50 GB	32 GB	12

If you also want to use the embedded database, you need to allow space for the data that it accumulates. For more information about how much space is required, please refer to the database and storage space requirements.

System requirements for multi-machine deployment

If you want to run scans on separate machines to your Enterprise server, then the following requirements apply.

Enterprise server machine

The machine on which you want to run your Enterprise server needs:

• Free disk space: 10 GB
• RAM: 16 GB
• CPU cores: 4

Scanning machine(s)

Each scanning machine requires a certain amount of resource to install and run the service that manages your scans, as well as additional resource to handle running the scans themselves. Therefore, the amount of extra resource needed varies depending on the number of concurrent scans you want to run.

	Free disk space	RAM	CPU cores
Base installation	10 GB	2 GB	2
Per concurrent scan	+ 20 GB	+ 8 GB	+ 4
Total for 1 scan	30 GB	10 GB	6
Total for 2 concurrent scans	50 GB	18 GB	10
Total for 4 concurrent scans	90 GB	34 GB	18

Kubernetes requirements

In order to deploy Burp Suite Enterprise Edition to Kubernetes, you need a cluster that meets the following requirements:

• An ingress solution, for example a load balancer or an ingress controller.
• A PersistentVolumeClaim called <application-name>-pvc that can be shared by all nodes in the namespace to which Burp Suite Enterprise Edition is going to be deployed.
• (Optionally) To enable cluster node autoscaling, the cluster-autoscaler must be installed and enabled.

Please note that you also need a database that meets the Burp Suite Enterprise Edition database requirements listed below.

Other than these prerequisites, Burp Suite Enterprise Edition should run on any x86-based cluster, irrespective of its underlying setup.

Database and storage space

The amount of data that is accumulated by Burp Suite Enterprise Edition depends on the number of scans that you perform and the number of issues found. The following table indicates the quantity of data that is likely to be accumulated:

Number of scans	Data storage
1,000	500 MB
10,000	5 GB
100,000	50 GB

Supported database versions

The following external database versions are fully supported:

Type	Supported versions
MariaDB	10.2, 10.3, 10.4, 10.5, 10.6
Microsoft SQL server	2012, 2014, 2016, 2017, 2019
MySQL	5.7, 8
Oracle	12.2, 18c, 19c
PostgreSQL	9.4, 9.5, 9.6, 10, 11, 12, 13, 14.2