Re: port scan and plugin selection

Two related Tenable blog entries:

Limiting the Ports Probed by Nessus Scans
http://blog.tenablesecurity.com/2006/09/limiting_the_po.html

Understanding the Nessus "Safe Checks" Option
http://blog.tenablesecurity.com/2006/09/understanding_t.html

If Nessus users have ideas or requests for more in-depth blog entries
(like the one we just did for using the 'nasl' binary), please feel free
to suggest something to me or Renaud off-list.

Ron Gula, CTO
Tenable Network Security


Will Cladek wrote:
> Sorry, I mean to ask how the "Optimize the test" option relates to
> this.  (Long day.)
>
> -Will
>
> Michel Arboi wrote:
> > Le Thu, 28 Jun 2007 17:03:15 -0400,
> > Will Cladek <william.cladek@nrl.navy.mil> a écrit :
> >
> > > How does the port scan portion of Nessus affect the plugins used?
> > > Are plugins only run against ports that are found to be open?
> >
> > No, most plugins are also run against a default port.
> > Anyway, find_service only run on open ports, and service identification
> > is necessary for many plugins. Disabling all port scanners is
> > definitely a bad idea.
> >
> > > If port scanning is disabled, are all plugins run by default?
> > >  How does the "Safe checks" option relate to this?
> >
> > There is no direct relationship in either case.
> _______________________________________________
> 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