Rich Whitcroft wrote:
> An example of this is the "Log details of the scan on the server"
> checkbox in the Options tab of the nessus client. Due to the volume of
> scans we'll be doing, as well as the log verbosity, I don't want to log
> every launched/not-launched nasl for every target host -- the log gets
> ridiculously large very quickly.
>
> ...
> The problem I see
> here is that I don't want nessus client users (sysadmins) to be able to
> check the "Log details of the scan on the server" (for example) and fill
> up my logs.
>
Why don't you just set a script to clean the area out every night?
e.g.
find /opt/nessus/var/nessus/users/ -name kbs - exec rm -rf {} \;
You could add exclusions around that, move to another area,
delete-if-older-than - all sorts of things...
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
