In my experience generally there are 2 things that slow a scan in OpenVAS.
Portscanning with nmap and in the vulnerability scanning some NVTs that can
hang. There 2 ways to find out what is happening. In a scan use the scan option
log_whole_attack and check openvassd.messages.log to see how much time
individual NVT take to run. The other way is to watch the processes related to
OpenVAS running.
If it is portscanning you need to adjust nmap timing parameters, in my opinion
by the default they are too permissive. In the NVTs you can configure a
parameter in the scan config to limit the maximum time an NVT can run.
Remember that reducing adjusting this parameters can have an impact of the
precision of the scan and by consequence of the results. In the end its a
choice Performance vs Precision.
Fabio.
> No dia 01/09/2017, às 15:56, Neeraj Shah
> escreveu:
>
> Gentleman, Can anybody advice how to fix slow scan issues ? I know this is a
> generic question and there can be many reasons for it. Is there any
> parameter or config that needs to tweaked on the OPENVAS server to fasten
> things up ?
>
> I am running un-authenticated FULL and FAST scans. One of the scans wherein
> i had defined 3 ip-addresses of my HOSTS as Target took around 4 hours to
> complete. On the other scan, i had defined a /24 network range as TARGET.
> It took 22 hours to complete even though there are only 12 hosts in that
> network.
>
> Are there any log files on OPENVAS side to debug ?
>
>
> Thanks in advance
> Neeraj Shah,
>
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss