Three Nessus 3.0.1 Questions, 1 Remark:
 
Question 1:
- nessusd.conf has max_hosts = 40
- nessusrc has max_hosts = 40
 
I submit multiple scan "jobs" to the scanning server simultaneously.  Does the 40-host limit apply to each job, or to nessusd overall?  That is, if I submit 10 jobs, each with 50 targets, will the server scan a maximum of 40 targets simultaneously, or 400?
 
I can't test this out because it's a [mostly] production environment.
 
Question 2:
What are the optimum max_hosts and max_checks values?  The scanning servers are all HP BL25p blades with 4 Gig RAM and dual processors, each processor is a 2600Mhz AMD with 64K L1 cache and 1024K L2 cache.  Hard drives are mirrored 172G 15,000 RPM SCSI. OS is 32-bit RHEL4.  The network is robust and the scans occur on weekends when traffic is minimal.  I'm currently using the defaults, max_hosts=40 and max_checks=5.
 
Question 3:
How does a simple iptable ruleset affect nessus' performance (if at all)?  When I run scans with iptables running, I occasionally see "dropped packet" messages.
 
Remark to Nessus 3 developer(s):
I am extremely pleased with the improved performance in this version!  Thank you for your talent and efforts.
 
Regards,
 
John Scherff
Sr. IT Security Analyst
24 Hour Fitness
 
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to