feat(waf): implement WAF detection earlier to adapt scan intensity #312
Description
Expected feature
WAF detection is currently implemented at the end in the workflow which is not a good practice because IP could be banned during the Pre-Crawl phase due to the big amount of request
It could be good to move the WAF detection (and also the screenshot phase) earlier in the Workflow
Best is to run WAF dectection task after the Initial task phase, so after sub discovery and OSINT.
This way, and according to the result, we could adapt the threads and delay to run less aggressive crawl, screenshot retrieval and active tasks (dir fuzz, nuclei ...)
Scan will be longer but safer and it should avoid get IP temporarily banned and force running another scan through proxy
Alternative solutions
No response
Anything else?
No response
Acknowledgements
- This issue is not a duplicate of an existing bug report.
- I have chosen an appropriate title.
- All requested information has been provided properly.