Error Running Validation Scan on Remediation Project

Hello,

Has anyone ever run into issues when trying to use the “Run Validation Scan” button on Remediation Projects? It doesn’t happen with every remediation project, but for many of them we receive an error stating, “Based on selected remediations, no scans could be started”. I haven’t been able to correlate what type of projects cause this, although as an example, it seems to happen with nearly every remediation project that involves patching browsers.

Has anyone else came across this issue? If so, were you able to solve it somehow or at least find out why it gives that error message? Due to this error, we are constantly having to run manual scans to make the vulnerabilities show as resolved under the remediation project.

This might be related to something I asked about the investigate option for a found vulnerability and that was what template and credentials does a validation scan run, and the answer was that it doesn’t use the custom ones so if there was a setting in a template or a specific credential needed it might not work. The other thing is if you are using Agents, this doesn’t use that, it initiates a normal scan. I stopped doing the validations, and just wait for the next scan cycle.

1 Like