Scan from the Dashboard
End-to-end narrative for running a DAST scan from the Levo UI — from creating the scan to exporting the report. If you've done the Quickstart, this page fills in the parts you skipped.
The happy path
- Create the scan → pick mode, target, auth, crawl depth, and tests.
- Monitor progress → watch crawl and active scan phases in real time.
- Triage findings → filter by severity, confirm, or dismiss as false positive.
- Export or send → download a SARIF/JSON report or push issues into your tracker.
- Schedule → re-run on a cron so drift gets caught automatically.
Detailed guides
➕
Create a scan
→
Walk through the 4-step Create DAST Scan dialog — mode, auth, crawling, security tests.
📈
Monitor scans
→
Track live progress, view logs, and stop runaway scans.
🛡️
Manage findings
→
Triage, group, and track vulnerabilities across scans.
🗓️
Schedule scans
→
Run on a cron or on every deploy.
📤
Export reports
→
Download SARIF, JSON, or PDF reports.
🛠️
Troubleshooting
→
Common dashboard issues and fixes.
Dashboard vs CLI — which should you use?
| You want to… | Use |
|---|---|
| Run a one-off scan and show results to someone | Dashboard |
| Let non-engineers trigger scans | Dashboard |
| Gate PRs in CI on scan results | CLI |
| Check a scan config into git | CLI with levo-dast.yml |
| Scan internal services behind your firewall | Both — use a Kubernetes worker |
Most teams use both: dashboard for ad-hoc investigation, CLI for CI enforcement.
Next → Create a scan
Was this page helpful?