﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / How to secure SQL Server audit log / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 10:38:58 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>Thanks guys, this looks like good stuff!</description><pubDate>Sun, 23 Aug 2009 11:18:36 GMT</pubDate><dc:creator>Richard Sisk</dc:creator></item><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>You can download the guide from here also. :-)</description><pubDate>Sun, 23 Aug 2009 08:37:55 GMT</pubDate><dc:creator>Sarab_SQLGeek</dc:creator></item><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>All you need is C2 Administrator’s and User’s Security Guide Revision 1.1you can donwload this guide from :http://www.microsoft.com/downloads/details.aspx?displaylang=en&amp;FamilyID=71C146F3-9907-40CD-BABF-3506ECD33254</description><pubDate>Sun, 23 Aug 2009 08:36:36 GMT</pubDate><dc:creator>Sarab_SQLGeek</dc:creator></item><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>- You can indeed switch your sqlserver instance to "audit login all", that will insert a row for every logon attempt in the sqlserver instance Errorlog file.Off course you'll have to secure that file at os level and take copies at frequent inverval,...- to trace what's going on you could use my little article " 	SQL Server and SOX" to get started. [url]http://www.sqlservercentral.com/articles/Security/3203/[/url]- Keep in mind at windows level  you can also audit the (windows) logons at os-level. - you can also capture sqlserver login events yourself ( see "Scope: The drastic caveat with Logon Triggers." ! at [url]http://www.sqlservercentral.com/articles/Administration/64974/[/url] )</description><pubDate>Sun, 23 Aug 2009 08:21:30 GMT</pubDate><dc:creator>ALZDBA</dc:creator></item><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>Sure,  its the log that gets the entries when someone does a login or logout of SQL Server. You can then view the logs in SQL Server Management Studio by clicking on Management/SQL Server Logs.</description><pubDate>Sun, 23 Aug 2009 07:25:33 GMT</pubDate><dc:creator>Richard Sisk</dc:creator></item><item><title>RE: How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>Can you elaborate on the audit logs you are referring to?</description><pubDate>Sun, 23 Aug 2009 00:13:36 GMT</pubDate><dc:creator>S. Kusen</dc:creator></item><item><title>How to secure SQL Server audit log</title><link>http://www.sqlservercentral.com/Forums/Topic775474-146-1.aspx</link><description>Working on instructions for securing a SQL 2005/2008 server for credit card PCI compliance. Below are the specific requirements from the PCI spec that I am using SQL Server auditing to cover.The specific items; 10.2.3 and 10.2.6 are the requirements I am solving for. Can I audit these actions?10.2.2 All actions taken by any individual with root or administrative privileges10.2.3 Access to all audit trails10.2.4 Invalid logical access attempts10.2 5 Use of identification and authentication mechanisms10.2.6 Initialization of the audit logsThanks</description><pubDate>Fri, 21 Aug 2009 16:23:39 GMT</pubDate><dc:creator>Richard Sisk</dc:creator></item></channel></rss>