highly dependent on the targets and the complexity of the scan. In my own experience, I've had the best performance with the linux client, but it's also pretty machine dependent. It's not like the windows or the mac ones suck by any means.
My guess is that if you had a fat box, not a lot of firewalls (particularly with rules that make it so hosts don't respond back), and were just doing a "Default" scan, it would take between 8 hours and 16 hours. However, that's a real guess... I've done a class B before, and it took about 10 hours, but it's so dependent on so many factors. On Fri, Nov 28, 2008 at 7:46 AM, Paul Jike <[EMAIL PROTECTED]> wrote: > I am planning to deploy Nessus as a tool for scanning a very large > network, locating the Windows hosts online, logging into these hosts > and retrieving a dozen registry keys. > The number of hosts that I expect to find in each scan is about 50000. > I am wondering how fast Nessus might be in collecting this data and > which architecture would deliver the best performance. > > Thank you in advance. > > Regards, > > Paul > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > -- Doug Nordwall Unix, Network, and Security Administrator You mean the vision is subject to low subscription rates?!!? - Scott Stone, on MMORPGs
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
