Skip to main content

Burp scanner reference for STO

You can scan your application instances using Burp Enterprise.

Important notes for running Burp scans in STO

Root access requirements

If you want to add trusted certificates to your scan images at runtime, you need to run the scan step with root access.

You can set up your STO scan images and pipelines to run scans as non-root and establish trust for your proxies using custom certificates. For more information, go to Configure STO to Download Images from a Private Registry.

For more information

The following topics contain useful information for setting up scanner integrations in STO:

Burp step settings for STO scans

The recommended workflow is add a Burp step to a Security Tests or CI Build stage and then configure it as described below.


Scan Mode

  • Orchestration Configure the step to run a scan and then ingest, normalize, and deduplicate the results.

Scan Configuration

The predefined configuration to use for the scan. All scan steps have at least one configuration.

The following configurations are available for Orchestration scans. These are built-in configurations provided by Burp Enterprise.

  • Default This is the same as the Crawl and Audit - Lightweight built-in configuration.
  • Never stop Crawl due to application errors
  • Never stop audit due to application errors
  • Minimize false positives
  • Minimize false negatives
  • Crawl strategy most complete
  • Crawl strategy more complete
  • Crawl strategy fastest
  • Crawl strategy faster
  • Crawl limit 60 minutes
  • Crawl limit 30 minutes
  • Crawl limit 10 minutes
  • Crawl and audit lightweight
  • Crawl and audit fast
  • Crawl and audit deep
  • Crawl and audit balanced
  • Audit coverage thorough
  • Audit coverage maximum
  • Audit checks medium active
  • Audit checks light active
  • Audit checks critical issues only
  • Audit checks all except time based detection methods
  • Audit checks all except java script analysis


  • Instance Scan a running application.

Target and variant detection

When auto-detect is enabled for application instances, the step detects these values as follows:

  • The target is based on the Instance Domain and Path defined in the step or runtime input, for example
  • The variant is the UTC timestamp when the step scanned the instance.

Note the following:

  • Auto-detection is not available when the Scan Mode is Ingestion.

  • Auto-detect is the default selection for new pipelines. Manual is the default for old pipelines, but you might find that neither radio button is selected in the UI.

  • You should carefully consider the baseline you want to specify for your instance target. Every target needs a baseline to enable the full suite of STO features. Here are a few options:

    • Specify a RegEx baseline that captures timestamps. This ensures that every new scan compares issues in the new scan vs. the previous scan. Then it updates the baseline to the current scan.

      You can use this RegEx to capture timestamps: \d{2}/\d{2}/\d{4}\,\s\d{2}\:\d{2}\:\d{2}

    • Specify a fixed baseline.

      1. Scan the instance using a manual variant name.
      2. Select the baseline as a fixed value.
      3. Update the step to use auto-detect for future scans.

      This ensures that future scans get compared with one fixed baseline.


The identifier for the target, such as codebaseAlpha or jsmith/myalphaservice. Descriptive target names make it much easier to navigate your scan data in the STO UI.

It is good practice to specify a baseline for every target.


The identifier for the specific variant to scan. This is usually the branch name, image tag, or product version. Harness maintains a historical trend for each variant.



Domain of the application instance to scan. Example:

Access Token

The access token used to log in to a specific product in the scanner. This is required for some scans. In most cases, this is a password or an API key.

You should create a Harness text secret with your encrypted token and reference the secret using the format <+secrets.getValue("project.container-access-id")>. For more information, go to Add and Reference Text Secrets.

Scan Tool

Use this setting to specify a specific scan to ingest. If this is not specified, the pipeline ingests the most recent scan.



Domain of the application instance to scan. You can include the full path to the app in this field, or split the full path between the Domain and the Path fields. Example:


HTTPS (default) or HTTP.


The TCP port used by the scanned app instance.


Path to append to the application instance domain, if you're splitting the full path between the Domain and Path settings. For example, you might specify the domain as and the path as /portal/us.


Username to log in to the instance you want to scan.


The access token to log in to the instance you want to scan. In most cases, this is a password or an API key.

You should create a Harness text secret with your encrypted token and reference the secret using the format <+secrets.getValue("project.container-access-id")>. For more information, go to Add and Reference Text Secrets.

Ingestion File

The path to your scan results when running an Ingestion scan, for example /shared/scan_results/myscan.latest.sarif.

  • The data file must be in a supported format for the scanner.

  • The data file must be accessible to the scan step. It's good practice to save your results files to a shared path in your stage. In the visual editor, go to the stage where you're running the scan. Then go to Overview > Shared Paths. You can also add the path to the YAML stage definition like this:

        - stage:
    - /shared/scan_results

Log Level

The minimum severity of the messages you want to include in your scan logs. You can specify one of the following:

  • INFO

Additional CLI flags

Use this field to run the scanner binary with additional flags supported by that scanner.


Passing CLI flags is an advanced feature. Some flags might not work in the context of STO. You should test your flags and arguments thoroughly before you use them in your Harness pipelines.

Fail on Severity

Every Security step has a Fail on Severity setting. If the scan finds any vulnerability with the specified severity level or higher, the pipeline fails automatically. You can specify one of the following:

  • HIGH
  • LOW
  • INFO
  • NONE — Do not fail on severity

The YAML definition looks like this: fail_on_severity : critical # | high | medium | low | info | none