Consider removing second target probe
Context
DAST currently performs 2 pings of the target to make sure that it is accessible before beginning the scan. The second uses ZAP as a proxy, and the first does not.
The second ping was ported over from the ZAP Python scripts. It isn't a desired feature, but we haven't been able to remove it because it changes the results of some scans while DAST is resetting the target to its host by default.
More details can be found in #258805 (closed)
What to do
If we can remove the probe
Remove the second target access check from CustomHooks
. It's the check that happens after the authentication logic.
If we cannot remove the probe
Remove the entire comment above the probe that links to this issue
Edited by Avielle Wolfe