ENTERPRISE

Configuring a Burp scan in Jenkins

  • Last updated: October 14, 2021

  • Read time: 3 Minutes

Configuring a Burp scan in Jenkins involves largely the same process as in previous versions of Burp Suite Enterprise Edition. In this section, we'll provide step-by-step instructions for the full configuration process.

Note

Although we continue to support the legacy "Burp scan" option, for most users, we recommend configuring a site-driven scan instead.

Prerequisites

Create the Burp scan build step in Jenkins

The following steps are the minimum configuration requirements to integrate Jenkins with Burp Suite Enterprise Edition.

  1. Log in to Jenkins.
  2. Open the pipeline in which you want to incorporate a vulnerability scan. Alternatively, create a new freestyle project if you just want to test the integration process.
  3. If you want to scan an existing site that you have already configured in Burp Suite Enterprise Edition, make sure your pipeline deploys this application to the same URL. Alternatively, if you do not want the scan to be matched with an existing site, make sure you deploy the application to a unique URL.
  4. Add either an "Execute shell" or "Execute Windows batch command" build step. In the "Command" field, enter a command that will echo the top-level URL of the running application that you want to scan and assign it to the variable BURP_SCAN_URL as follows:
    echo BURP_SCAN_URL = https://application-to-scan.com
    This step will output the target URL in its build log in the correct format for the plugin to process in the next step. If you have a more dynamic deployment process, for example, to a Docker container, you should repeat this command multiple times to output each of the relevant URLs. All of these will be aggregated and scanned.
  5. Add another new build step, but this time select the type "Burp scan".
  6. Enter the URL of your Burp Suite Enterprise Edition REST API endpoint. This is the URL that you copied after creating the API user earlier. Make sure you include the appropriate protocol and port.
    • If you want to be able to download scan reports, exclude the API key from this URL as follows and instead enter the API key in the dedicated field beneath. This is the recommended approach.
      URL: https://your-enterprise-server:8080
      API key: your-api-key
    • If you do not want to download scan reports, you can include the API in the URL. In this case, you should leave the API key field blank. We do not recommend this approach as it is primarily to provide continued support for legacy integrations that were configured before we adjusted the input fields.
      URL: https://your-enterprise-server:8080/api/your-api-key
      API key: [blank]
  7. Adjust the various optional settings to fine-tune how the scan and its results will affect your build. For "Burp scans", you also have the options to:
    • Upload a custom scan definition to either customize the scan configuration for a one-time scan or override the default configuration for the matched site.
    • Define rules for ignoring issues. This is useful for setting false positives for a "Burp scan".
      Note that this option is not available for "site-driven scans" because they inherit false positive rules from their associated site in Burp Suite Enterprise Edition.
  8. Save your pipeline.

Test your integration

After you finish configuring the build step, it's a good idea to check whether the integration is working correctly and that your scan is able to run successfully.

  1. Kick off a build on demand and look at the console output in Jenkins. You should see the scan initialize and start crawling. Throughout the scan, you can check the status by monitoring the console output for the build. Issues that are found will also be output to the console.
  2. In Burp Suite Enterprise Edition, go to your site and open the "Scans" tab. You should see the Jenkins-initiated scan in the list.