November 6, 2009 at 9:33 am
Ok, our company just went through an external audit and I got flagged for not having my SQL log files locked. They said that I need to have each log file protected, so they can not be altered by anyone. I know the initial 'errorlog' is locked while it is being used, but what is the best route for locking the other log files; errorlog.1 -> errorlog.6. Is there an application that I can run that would keep these files from being edited until they are deleted? Is there a setting in SQL I do not know about? I don't want to get into a manual process, as that would be a maintenance nightmare with so many servers. I am not sure where to begin on this, so I thought I would ask what you guys are doing and how you protect your sql log files.
Thanks in Advance!
November 6, 2009 at 9:59 am
Hi
You can use a SQLCLR procedure or a SSIS script task using .NET to encrypt the files or move them into a database table.
Greets
Flo
November 6, 2009 at 10:04 am
Another method is to setup a scheduled job to copy them to another location (commonly a central location for log files) that is firewalled, protected and on an encrypted file system. This process allows for file comparison by having multiple copies. Auditors are usually ok with this method.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply