p.remek1 at googlemail
Sep 30, 2008, 6:24 AM
Post #5 of 6
As I am curious too I will add my findings. I have set up nessus to scan
one IP address for single one port (23), with all plugins and all other
stuff turned off.
Even with this minimal setting I can see lot of data going out to the scan
I have captured about 130-150 packets going to and from various ports
The scan takes 35 seconds to complete, target box is on LAN.
On Mon, Sep 29, 2008 at 2:48 PM, Ron Gula <rgula [at] tenablesecurity> wrote:
> Mike.Vasquez [at] cityofmesa wrote:
> > I'm looking at using Nessus for some general port scanning, so that i can
> > have all results consolidated in Security Center. I really want to limit
> > scanning to a port or 2, and limit the hosts to just a handful at a time,
> > to limit network traffic during the scan.
> > My initial testing seemed to indicate that it was taking about a minute
> > and a half per IP. That was much longer than I expected. I was checking
> > for 2 open ports, 2 IPs at a time, no plugins running, all on a LAN, SYN
> > scan.
> > Wondering if it's a case of using the wrong tool, or if there are
> > additional settings/tweaks I should consider. Any input appreciated.
> Hi Mike,
> We're you performing the test under SC3 or under a Nessus Client?
> If you limited the scanned ports to just two ports, the scan should not
> have taken that long. I'm curious if you had any other plugins enabled
> such as service fingerprinting.
> Ron Gula
> Nessus mailing list
> Nessus [at] list