The TCP port used by the scanned app instance.
#Burp scanner full
You can include the full path to the app in this field, or split the full path between the Domain and the Path fields.
Instance settings Domain ĭomain of the application instance to scan. If this is not specified, the pipeline ingests the most recent scan. Use this setting to specify a specific scan to ingest. For more information, go to Add and Reference Text Secrets. You should create a Harness text secret with your encrypted token and reference the secret using the format. In most cases, this is a password or an API key. The access token used to log in to a specific product in the scanner. Authentication settings Domain ĭomain of the application instance to scan. This makes navigating your scan results in the STO UI much easier. Make sure that you give unique, descriptive names for the target and variant. Audit checks all except java script analysis.Audit checks all except time based detection methods.Never stop audit due to application errors.Never stop Crawl due to application errors.Default This is the same as the Crawl and Audit - Lightweight built-in configuration.These are built-in configurations provided by Burp Enterprise. The following configurations are available for Orchestrated scans. All scan steps have at least one configuration. The predefined configuration to use for the scan. The Security step ingest results from a previous scan (for a scan run in an previous step) and then normallizes and compresses the results. Ingestion Ingestion scans are not orchestrated.A Security step in the Harness pipeline orchestrates a scan and then normalizes and compresses the results. Orchestrated A fully-orchestrated scan.
The following list includes the UI and YAML values for the supported options.
The orchestration mode to use for the scan.
0 kommentar(er)
