DAST action
Last updated: Nov 11, 2026
The DAST action runs Fluid Attacks' dynamic application security testing scanner in your GitHub Actions workflows. It detects vulnerabilities in your live web application. To do this, it sends requests to the URLs that you configure.
If you want, you can attribute the runs to your Fluid Attacks group. For the setup, read Authentication.
Marketplace: fluidattacks/dast-action
Setup
1. Create the configuration file
Create a YAML configuration file in a location that you select in your repository.
For example, .github/dast-config.yaml:
language: EN
strict: false
output:
file_path: results-dast.sarif
format: SARIF
dast:
urls:
- url: https://www.myapp.com
- url: https://www.myapp.com/apilanguage— language for vulnerability descriptions in the output (ENfor English,ESfor Spanish).strict— whenfalse, the scanner reports findings but does not fail the pipeline. Set it totrueto break the build when the scanner detects a vulnerability. Thestrictaction input overrides this value.strictness_threshold— optional severity (low,medium,high, orcritical). The scan breaks the build only for vulnerabilities at or above it. Thestrictness_thresholdaction input overrides this value.output.file_path— path where the scanner writes the results. When the format isSARIF, thesarif_fileaction output also shows this path.output.format—SARIFgives the standard format that GitHub's code scanning API uses. UseCSVfor a report that you can open in a spreadsheet.dast.urls— list of URLs that the scanner sends requests to. The target application must run and the GitHub Actions runner must have access to it.
2. Create the workflow
Add .github/workflows/dast.yml to your repository:
name: DAST
on:
push:
pull_request:
types: [opened, synchronize, reopened]
schedule:
- cron: "0 8 * * 1" # optional: weekly scan every Monday at 8am
jobs:
scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: fluidattacks/dast-action@<version>
id: scan
with:
scan_config_path: .github/dast-config.yamlNote: Replace <version> with the latest release tag. Find it on the Marketplace
page.
- When the workflow runs, the target application must be public or the runner must have access to it.
3. Push and run
Commit the two files and push. The scan runs automatically on the subsequent push or pull request.
Action inputs
| Input | Required | Default | Description |
|---|---|---|---|
scan_config_path | Yes | — | Path to the YAML configuration file, relative to the repository root. The job fails immediately if the file does not exist at that path. |
strict | No | — | true or false. Set it to true to break the build when the scan finds vulnerabilities. It overrides strict in your configuration file. If you omit it, the configuration file decides. For more information, read Strict mode. |
strictness_threshold | No | — | low, medium, high, or critical. Breaks the build only for vulnerabilities at or above this severity. It overrides strictness_threshold in your configuration file. If you omit it, the configuration file decides. For more information, read Strict mode. |
group | No | — | Your Fluid Attacks group. The action gives it to the scanner as --group. For a short-lived OIDC token, the workflow must have the id-token: write permission, and the group must have a trust for the repository. If you give neither this input nor api_token, or the action gets no credentials (for example, in a pull request from a fork), the scan runs without authentication. |
api_token | No | — | Long-lived Group token for workflows that cannot use OIDC. Give it from a secret, for example ${{ secrets.FA_API_TOKEN }}. If you give this input, the action uses it and not OIDC. The token identifies the group, so you do not need the group input. |
Action outputs
| Output | Description |
|---|---|
sarif_file | Path to the SARIF results file (only set when output.format is SARIF) |
vulnerabilities_found | true if the scan found vulnerabilities at or above the threshold that applies, false otherwise |
You can use these outputs in the subsequent workflow steps:
- name: Comment on PR
if: steps.scan.outputs.vulnerabilities_found == 'true'
run: echo "Vulnerabilities detected — check the Security tab."Common scenarios
Scan a staging environment on pull requests only
on:
pull_request:
types: [opened, synchronize, reopened]In your configuration file, use the URL of a staging environment that the PR workflow deploys.
Strict mode: block merges with vulnerabilities
Set strict: true to fail on any vulnerability,
or strictness_threshold to fail only from a severity up.
You can set them as action inputs or in your configuration file:
- uses: fluidattacks/dast-action@<version>
with:
scan_config_path: .github/dast-config.yaml
strictness_threshold: highFor common scenarios and troubleshooting, read GitHub Actions.
Fail the pipeline when an endpoint is unreachable
Set dast.strict_connectivity: true to exit with a non-zero status code
if the scanner cannot get to a configured URL during the scan.
This helps you find configuration or environment problems.
An empty result then means that the scan found no vulnerabilities.
dast:
strict_connectivity: true
urls:
- url: https://www.myapp.comTroubleshooting
No results appear in the Security tab
You cannot upload DAST findings to the GitHub Security tab. GitHub's code scanning API requires a specific file and line number for each vulnerability. Web application vulnerabilities detected at runtime do not have this information.
To examine DAST results, use the output file of the scanner.
Set output.format: SARIF or CSV in your configuration file and read the file
as a workflow artifact, or send it to a reporting tool that you select.
The scanner cannot reach the target URL
The GitHub Actions runner must have network access to the URLs configured in dast.urls.
For private or internal URLs, you must use a self-hosted runner on the same network.
For common scenarios and troubleshooting, read GitHub Actions.
Read the Marketplace page for all the configuration options and more troubleshooting.