Monitoring Scan Progress

Track your scans in real-time and understand the execution stages.

Real-Time Status

The scan details page provides live updates:

• Current Activity: What the scanner is currently testing
• Pages Crawled: Number of pages/endpoints discovered
• Tests Executed: Total security tests performed
• Findings Count: Vulnerabilities discovered so far (by severity)

Scan Status

A scan reports one of four statuses on the dashboard:

Status	Meaning
Queued	Waiting for a worker to pick up the job.
Running	Worker is executing the scan — crawling, testing, and analysis all happen under this state. Live counters (Pages Crawled, Tests Executed, Findings) update as work progresses.
Completed	Scan finished successfully. Findings are available under the Findings tab.
Failed	Scan could not complete. See the Logs tab for the error, then Troubleshooting.

Controlling Scans

Cancelling Scans

• Cancelling: Cancel the current scan
  • Results collected so far are saved
  • You can still view partial findings
  • A new scan must be started for complete coverage
  • Click Cancel in the scan details page

Restarting Scans

• Restart: Re-run a completed scan with the same configuration
  • Uses identical settings from previous scan
  • Useful for comparing results over time
  • Click Restart from scan history

Interpreting Scan Statistics

Finding Count by Severity

Scans classify vulnerabilities into severity levels:

• Critical - Immediate exploitation risk, severe impact
• High - Significant vulnerabilities that should be addressed quickly
• Medium - Notable security issues requiring attention
• Low - Minor issues or hardening recommendations
• Info - Informational findings, no direct security risk

Performance Metrics

• Pages Crawled: Total endpoints/pages discovered
• Tests Executed: Number of individual security tests run

Timing Information

• Elapsed Time: How long the scan has been running
• Start Time: When the scan was initiated
• Completion Time: When the scan finished

Monitoring Multiple Scans

Scan History

View all your scans from the DAST Scans page:

• Sort by: Status, date, findings count, or application
• Filter by: Application, status, etc
• Search: Find scans by name or target URL

Best Practices

Interpreting Results During Execution

1. Don't interrupt long scans prematurely

   • A scan can stay in Running for a long time on large apps — watch the live counters instead of restarting.
   • Restarting throws away findings collected so far.

2. Monitor for errors

   • Check scan logs if progress stalls
   • Look for authentication failures
   • Verify target URL accessibility

3. Track trends

   • Compare finding counts across scans
   • Monitor newly introduced vulnerabilities
   • Track remediation progress

Next Steps

Once your scan completes, review and manage the findings:

• View and Manage Findings - Analyze security vulnerabilities