Nessus Option?

Can you explain a bit more what you mean by "desired results"?
If you know a particular security hole does not get detected, you got
to figure out the plugin that does the test for it, and see if it has
run, and why if it did not give the right results. Running a plugin on
a closed port won't be of any use. Also, running all plugins on all open
ports --- I am not even sure if that will work, since plugins run on
specific ports or specific services. For instance, if the port scanner
(which runs first) finds that an http service is running on a particular
port, then all plugins meant for http services will be run on that port.
If the specific KB entry meant for http services is not filled, then all
plugins for http services will run on port 80 (default port meant for
http).

regards,
Samir Kelekar
Teknotrends Software

plugins) that tells it 

Hi folks

Is it somehow possible to tell Nessus, that it should try all plugins on
all ports - independent of what ports are open? I know that's a stupid and
brute way to test, but I have a strange system which does not produce the
desired results when using Nessus intelligence (I already played with
"enable dependencies at runtime", "safe checks" and "optimize tests").

Any hint welcome...

GreetZ from IndianZ

mailto:indianz@indianz.ch
http://www.indianz.ch
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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