Regards,
I have two questions regarding Nessus scanning across firewalls. We have
experienced network congestion/slowness when running Nessus inside a
firewall protected network against hosts on the "other side". We use
Nessus 3.0.4 and did not enable the nmap wrapper, ie using Nessus
internal port scanner to scan all ports (65535). We limited checks to 5
simultaneous hosts, 5 simultaneous checks. We also turned on throttle
scan and network congestion detection. Even though these precautions
were taken, the network suffered. Apparently this was caused by ports
being held open for too long during the scanning period, making the
firewall drop old connections. Unfortunately I cannot reveal further
details. Is Nessus 3 this intrusive ? What can be done to further limit
network impact when testing across firewalls ?
***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
|