DAST prints spidered results once spidering is complete
Problem to solve
At the moment, spidered results are printed at the end of a DAST Scan. This causes problems with users who are trying to diagnose scans that take a long time. This is because if the scan takes too long, the job times out and the spidered results are never displayed on the log.
Proposal
Print the spidered results to the log as soon as spidering is complete. This should apply for passive and active scans.
Screenshot of logged spidered results
Intended users
User experience goal
Find out spidered results sooner.
Technical Implementation
Inject a hook into the ZAP Python scripts that fires once spidering is complete. Listen to the hook, and print the spidered results exactly as they are now.
Documentation
Availability & Testing
The test that verifies spidered scan results should be sufficient, and should still pass.