On Tue, Jan 18, 2011 at 8:56 AM, Peter Addy <[email protected]> wrote:
> does anyone have any good practices and just general thoughts on saving > policy > packages and DB control > > right now we simply push a policy with the same name and make sure we have > DB > control set at all times. > > Does anyone out there save a new policy package as a new name, date etc, > and if > so why, is it better to save a new package each time a change is made, or > will > db control suffice, or do you do both?. > > Just wondering what the norm was and what the best best practices is > Thanks > > > As long as you are backing up the manager the DB control is sufficient. We have had cases where we renamed some of the packages to the date due to some specific requirements. One example was that some crontab scripts would do checks for new policies by running 'fw stat' on the firewall. The script would then use the name for its processing. If you're not doing something like that then keeping the one name and a small history of revisions is fine. -- ciao JT ================================================= To set vacation, Out-Of-Office, or away messages, send an email to [email protected] in the BODY of the email add: set fw-1-mailinglist nomail ================================================= To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================= If you have any questions on how to change your subscription options, email [email protected] =================================================
