PortSwigger Research
PortSwigger documentation explains how Burp Suite DAST tracks issues over time, classifying them as new, regressed, repeated, or resolved, and raises Jira tickets automatically based on that classification. It manages tickets per Jira project separately,...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger documented how to connect Burp Suite DAST to Trello so that scan findings can be turned into Trello cards, either manually from within DAST or automatically for issues meeting specified minimum severity and confidence levels. The guide...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how Burp Suite DAST connects to Jira Cloud and Jira Data Center up to 10.x, with 8.4.1 as the oldest supported version, so users can raise Jira tickets directly from the scanner. The integration requires linking DAST...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger documents how to link Burp Suite DAST to GitLab so scans can raise GitLab issues, either manually or automatically, using a dedicated GitLab user added as a Reporter to selected projects and an impersonation token. The guide notes that the...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes conditional field mapping in Burp Suite DAST, which lets multiple rules map different values to Jira custom fields based on an issue's severity and confidence. The text warns that overlapping severity and confidence...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how Burp Suite DAST connects to issue tracking platforms including Jira, GitHub, GitLab, Trello, and ServiceNow. The guide covers raising tickets from within DAST, automatic Jira ticket creation, conditional field...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how users with extension-management permission view, update, and delete extensions in Burp Suite DAST through the Extension library, which separates BChecks, BApps, and custom extensions into tabs. Custom extensions...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how extensions added to Burp Suite DAST are uploaded to a central Extension library, where users with the Manage extensions permission can apply them to specific sites during scans. It notes that extensions run on the...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes optional settings for its CI/CD integration with Burp Suite DAST, letting teams set thresholds that fail a build: minimum issue severity (default medium), minimum confidence (default tentative), and a permitted issue...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation states that Burp Suite DAST offers two CI/CD integration options: site-driven scans, which let the CI/CD system pull site tree details, default scan configurations, false positive settings, and included/excluded URLs from the...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published parameter reference documentation for the generic, platform-agnostic CI/CD driver that integrates a Burp Suite DAST scan into pipelines, covering required inputs such as the DAST server URL, API key, and site ID, plus optional...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes its legacy CI/CD integration for Burp Suite DAST, which provided plugins for Jenkins and TeamCity plus a generic driver for other platforms, and is now maintained only for users already on that approach. The legacy...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's guide describes integrating Burp Scanner into any container-supporting CI/CD platform by running a Docker command in the pipeline script, configured with the DAST server URL, an API key from a CI-driven scan initiator group, and the target...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published instructions for integrating a CI-driven Burp Scanner scan into TeamCity, letting teams run scans as a stage in an existing CI/CD pipeline and fail builds when issue thresholds are met. The scan is configured through parameters in a...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published instructions for integrating a CI-driven Burp Scanner scan into Jenkins, running scans as a stage in an existing CI/CD pipeline and failing builds when issue thresholds are met. The scan is configured through simple parameters in a...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published instructions for integrating a CI-driven Burp Scanner scan into GitLab, letting teams run scans as a stage in their existing CI/CD pipeline and fail builds when issue thresholds are met. The setup requires a deployed Burp Suite DAST...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger documents a way to integrate a CI-driven scan with GitHub Actions, letting Burp Scanner run scans as a stage in an existing CI/CD pipeline and fail builds that meet a set issue threshold. Scans can be configured with a configuration file, which...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published instructions for integrating a CI-driven Burp Scanner scan into an Azure DevOps pipeline, running the scan as a pipeline stage and failing builds with a non-zero exit code when issue thresholds in the YAML configuration are met. The...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger published platform-specific integration examples for adding CI-driven scans to pipeline scripts, covering how to add the scan command and configuration YAML file. The guides state that CI-driven scans can be integrated and configured with any...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's guide describes a YAML template for configuring CI-driven Burp Suite DAST scans, requiring a DAST server URL and API key (enterpriseServer.url and enterpriseServer.apiKey) plus start URLs for web app scans or an API definition file or URL for...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation states that running CI-driven scans in Burp Suite DAST requires network and firewall configuration, with different requirements for Cloud and self-hosted instances. Both setups require outbound access from scan containers to...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's Burp Scanner can now run as a CI-driven scan, spinning up an instance of the scanner inside a Docker container that performs a local scan on a URL set by an environment variable in the pipeline script. When the scan finishes, that instance...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how to run common Burp Suite DAST operations through its GraphQL API, including queries for scan status, per-scan issue counts by severity, scan configurations, and the site tree, plus mutations to create sites,...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation describes how to use the GraphQL API to integrate Burp Suite DAST with your own or third-party software, requiring a dedicated API user whose permissions limit what the API can do. All operations are sent as POST requests to...
Vulnerabilities & Patching
PortSwigger Research
Burp Suite DAST provides two APIs for interacting with the system from third-party software: a GraphQL API, which PortSwigger recommends for new integrations and describes as offering the broadest range of functionality, and a REST API, positioned as a...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's guide to running a first scan in Burp Suite DAST describes an onboarding wizard that has users create a "site" by entering a site name and a start URL, with sub-paths of that URL included in scan scope by default. Users pick from four preset...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's quick start guide for Burp Suite DAST walks through installing a standard single-machine instance with default settings, recommending at least 8 CPU cores and 24 GB of RAM, which supports one concurrent scan only. The guide notes the web...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's tutorial walks through Burp Suite DAST's scan-result views: the Overview tab's charts update in real time while a scan runs, and the Issues tab lists findings color-coded by estimated severity and grouped by issue type, expandable to the URLs...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's documentation lays out three deployment methods for Burp Suite DAST: a standard install on physical or virtual Windows or Linux machines including cloud VMs and headless servers, a Kubernetes option for teams already running Helm charts and...
Vulnerabilities & Patching
PortSwigger Research
PortSwigger's installation guidance for Burp Suite DAST states that standard instances default to port 8080 for HTTP or 8443 for HTTPS, and that TLS configuration is optional but recommended for production. The document also says installations require...
Vulnerabilities & Patching