Re: How long should Nessus take to do a full scan?

Pete Duffin wrote:

> What do you have set as your port range.  When I select to scan all 
> ports, it takes much more time than that.  When I have it set to run 
> just the known ports, its more like 15 minutes.

port_range = default

I actually want all ports scanned (which the above will miss I think - I 
didn't notice that before). This is a scheduled job that is scanning 
DMZes, and I want to know if someone has brought up a Web server on port 
43223 if it happens...

> Also, do you have "Optimize Scan" checked?  That will make it so 
> nessus does not run checks that are not pertainent.

Yup that's set.

Also, "Thorough tests" is disabled, "Enable experimental scripts = no", 
"safe_checks = no" (as this is meant to be a "full scan" - I don't want 
any assumptions made).

Also, Michel asked what the longest test took to complete - the "top 20" 
times ranged from 50 to 250 seconds. The slowest tests are 
"DDI_Directory_Scanner.nasl", "goodtech_ftpd_dos.nasl", 
"tomcat_devname_DoS.nasl", "miscflood.nasl". However, none of those 
tests are in the 2000 sec range - we couldn't be that lucky ;-)

--
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus