Managing updates

  • Last updated: September 9, 2021

  • Read time: 2 Minutes

Click the settings icon and select "Updates". From there, you can see details about the currently installed software and any available updates.

There are two separate components shown, each of which might have pending updates:

There are configuration options for automatic updates. You can also manually check for updates and apply pending updates at any time. Applying updates either automatically or manually might result in some downtime.

Note: To perform any kind of update, the Enterprise server needs network access to https://portswigger.net.

Offline updates

If your installation is unable to contact the PortSwigger updates server, you can perform an offline update of both Burp Suite Enterprise Edition and Burp Scanner. You can manually download updates from your PortSwigger account. Then use the "Upload ZIP file" button to upload the update.

Downtime during updates

The impact of applying an update in terms of application downtime is as follows:

  • Updates to Burp Suite Enterprise Edition will cause some downtime while the update is applied. The web UI, REST API, and GraphQL API will be unavailable during the update, and any scans that are configured to start during the update will be delayed until it is completed. Scans that are already running at the time of the update are unaffected. To reduce the impact of downtime, you can configure whether to restrict automatic updates of Burp Suite Enterprise Edition to specific days and times.
  • Updates to Burp Scanner do not cause any downtime. Scans that are already running at the time of the update will continue using the version of Burp Scanner that they started with. New scans that start after the update will use the updated version of Burp Scanner. It is generally desirable to enable automatic updates of Burp Scanner to ensure that the latest scan checks are available.

Over time, there might be backwards compatibility limitations on either component in relation to the other. If one component has not been updated for some time, then it might be that it must be updated before any further updates can be made to the other component. The updates page will indicate when this is the case.

Some available updates might require manual intervention preventing them from being applied automatically. For example, if an available update makes changes to the software license agreement, then it may be necessary to accept the new agreement before the update can be applied. The updates page will indicate when this is the case.