DAST scanner

Last updated: Oct 20, 2026

For common configuration file keys that apply to all scanners, see Use a configuration file.

Specific configuration file keys

The following keys are available only for the DAST scanner, nested under the dast key:

strict_connectivity

When set to true, the scanner exits with a non-zero status code if any configured endpoint could not be reached during the scan. Defaults to false.

dast:
  strict_connectivity: true

urls

A list of URLs to analyze. Each entry requires a url field and accepts an optional environment_id field:

dast:
  urls:
    - url: https://my-app.com
    - url: http://localhost
      environment_id: my-environment

Configuration file example

Below is an example of a highly personalized configuration file:

namespace: my_app
working_dir: ./
commit: e59607b9de3ef4c13d292705fg3da1ff0c67eb38
language: EN
output:
  file_path: /fluid-attacks-results.csv
  format: CSV
checks:
  - F043
strict: true
dast:
  strict_connectivity: true
  urls:
    - url: https://www.my_app.com