RE: Scheduling Nessus Scans

Although I'm using suse 10 as well I don't think the distro matters that
much. As I see it there are two basic approaches: cron job vs. service.

Although I setup snort as a service I am using cron to manage nessus. The
difference is that I want snort to be started whenever the box comes up
whereas nessus is used to conduct specific scans.

I wrote a wrapper script to handle the flexibility you describe (plugins,
authentication, IPs to scan, etc.). It manages the IP scanning by modding
the current time in seconds by the number of subnets defined for scanning.
This gives a more or less continuous scan of our network.

Tim Doty

-----Original Message-----
From: nessus-bounces@list.nessus.org [mailto:nessus-bounces@list.nessus.org]
On Behalf Of Bledsoe, Horace W.
Sent: Wednesday, July 12, 2006 9:12 AM
To: Nessus@list.nessus.org
Subject: Scheduling Nessus Scans

Hello all,  I am a newbie to Linux and was wondering what would be the best
approach to schedule a nessus scans from a suse 10 box?

It sounds like cron jobs are able to kick off the process, but can it
specify plugins, authentication, IPs to scan, etc? Or, would I need a script
for cron to run at a certain time?

Any thoughts are welcomed.  Thanks

Horace Bledsoe


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

smime.p7s
Description: S/MIME cryptographic signature

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