Blog Archives

Auditing Revisited, Makes No Sense To Me

Back in January, I did a series on simple auditing which walked through setting up an audit and creating a simple SSRS report.  I actually used the report and the query that I demonstrated for a couple of servers in my stack that require auditing.  The basis of this revolves around the following line of code:

SELECT * FROM fn_get_audit_file (‘g:\auditing\*’, DEFAULT, DEFAULT)

This line of code runs great for my login and I never gave it much thought because I am running it from a sysadmin account.  When asked for users to be able to run this report that is when things are getting sticky.  I cannot fathom why a simple query for log data cannot be attributed to a read-only account.  In order for you to run this select statement you either need a sysadmin level account or the CONTROL SERVER permission which pretty much gives you the keys to the kingdom.  Why would they do that?

I am sure there is a great technical reason, but why not allow it to filter down to read-only access to simply view the data?  With those permissions whoever is in charge of running the audit can manipulate the data however they see fit.  That makes no sense to me but then again who am I in the grand scheme of things?  Shortly I will post a few different scenarios in how to solve this problem.  Enjoy!

SQL Server Auditing: A Learning Series Part Nine, Reporting

Continuing our learning series on auditing, today we look at the next logical step:  Reporting.  We have created audits for the server and for the database as well as being able to query the audits, but what good is an audit if you cannot print a report and hand it to the auditors?

Having been a developer and admin in my past life, you may find it strange that I have never before today created a SQL Server Reporting Services report.  Now don’t get me wrong, I have written a boat load of reports in many other formats (crystal, web, actuate, etc) but have never really had the opportunity or the pleasure to write in my preferred environment.

Given the following function, I thought reporting would be a little more difficult:

SELECT * FROM fn_get_audit_file (‘g:\auditing\*’, DEFAULT, DEFAULT)

This arguments for this function are (file_pattern, initial_file_name, audit_file_offset).  The file_pattern argument must include a path and a filename but can include a wildcard.    The initial_file_name argument must specify the path and name of a specific file in the file set to start reading the records from or the DEFAULT|NULL value.  The audit_file_offset argument will beginning reading the first record after the specified offset (which is a field that can be queried with the function).

Now on to the report….

  1. Open Visual Studio and choose  File –> New Project.
  2. Select Report Server Project Wizard and name the project appropriately.
  3. Enter your connection information and credentials.
  4. When prompted to design the query enter the query above as shown in Figure 1.
  5. Select additional reporting options as your preferences allow and then save the report.
rptwizquery

Figure 1 – Report Wizard Query String

This concludes our series on auditing, I hope you found it helpful!

SQL Server Auditing: A Learning Series Part Nine

Continuing our learning series on auditing, today we prepare for a database audit.  Just like with the server audit specification, you must setup a new server audit that correlates to this database audit specification (remember, it is a one-to-one relationship).

  1. Create a new server audit for your database audit as demonstrated in part three of this series.
  2. In SQL Server Management Studio, select the database for which you plan to audit.
  3. Then select the Security node followed by right-clicking on Database Audit Specification and select New Database Audit Specification.
  4. From here, the directions are the same as was demonstrated in part five of this series except here we can select the Object Class of either DATABASE, OBJECT, or SCHEMA.  For example if we audit the UPDATE action then we can choose the object upon to audit.

Enjoy and stay tuned.

SQL Server Auditing: A Learning Series Part Eight

Continuing our learning series on auditing, today we discuss a couple of caveats to close out the week before we create database audits next week.

  1. In order to CREATE, ALTER, or DROP on either the server audit or server audit specification, the security principle must be assigned to ALTER ANY SERVER AUDIT or CONTROL SERVER permission.
  2. You can rename an Audit but not a server audit specification so choose your name wisely.
  3. In order to modify the properties of either the server audit or server audit specification, you must disable them and then re-enable them after your changes are completed.
  4. In order to CREATE, ALTER, or DROP a database audit specification, the security principle must be assigned to ALTER ANY DATABASE AUDIT or the ALTER or CONTROL permission on the respective database as well as having the permission in order to connect to the database.

Enjoy and stay tuned as we continue the series next week!

SQL Server Auditing: A Learning Series Part Seven

Continuing our learning series on auditing, today we look at how to query the audit information from the server.

  • sys,server_audits displays information on the audits setup on the server.

    sysserveraudits

    Figure 1 – Sys.server_audits

  • sys.server_audit_specifications displays information on the audit specification setup on the server.

    sysserverauditspec

    Figure 2 – Sys.server_audit_specification

  • sys.server_audit_specification_details display detailed information about the specifications.

    Figure 3 - Sys.server.audit.specification.detail

    Figure 3 – Sys.server.audit.specification.detail

  • sys.dm_server_audit_status displays information about the status of your audits.

    Figure 4 - Sys.dm_server_audit_status

    Figure 4 – Sys.dm_server_audit_status

Enjoy and stay tuned!

SQL Server Auditing: A Learning Series Part Six

Continuing our learning series on auditing, today we look at the results from the audit specification that we created yesterday.  In this audit specification we are monitoring for database ownership change or permission change.  I changed the owner on one of the databases on the server and an audit log entry was generated as shown in Figure 1.  We can see who changed the ownership and what it was changed to.  I think it would be better to show me what the original value was.  Enjoy and stay tuned!

audit results

Figure 1 – Audit Results

SQL Server Auditing: A Learning Series Part Five

newsauditspec

Figure 1 – Create a new Audit Specification

Continuing our learning series on auditing, today we create a new audit specification (as explained in last week’s post).  Remember, in order to create a new server audit specification, you must have created a new server audit.  This is a one-to-one relationship and in order to actually collect auditing information both objects are required.

Think of it like an order table that has to have an order lines table in order for a sales order to be made, if that helps your understanding.

  1. In the security node of SQL Server Management Studio, right-click on Server Audit Specification and select New Server Audit Specification, as shown in Figure 1.
  2. Change the name and use the drop down selections to select the type of server audits you would like to audit, as seen in Figure 2.  (MSDN explanation of groups and actions)
  3. Right-click on the Server Audit Specification in the Security node and select enable to activate your new audit specification.
servauditspec

Figure 2 – Create Server Audit Specification

You can alternatively script this as well:

CREATE SERVER AUDIT SPECIFICATION [ChangingPermOwner]
FOR SERVER AUDIT [Audit-Test]
ADD (DATABASE_OBJECT_PERMISSION_CHANGE_GROUP),
ADD (DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP)
WITH (STATE = ON)
GO

Enjoy and stay tuned!

SQL Server Auditing: A Learning Series Part Four

Today we continue our series on Auditing with some clarifications.  An audit is essentially the combination of several elements.  This concept took a day or two to wrap around my brain so I thought I would discuss our way through it.

  1. The Audit Object is collected on either the server or database level.  This covers actions as well as groups of actions.
  2. The Audit Specification is an object that belongs to an audit.  This is a one-to-one relationship between audit object and audit specification.  Both items are created at the instance level.  The audit specification can collect many server-level or database-level action groups which are raised through extended events. You can have many groups within a specification.  In addition, the audit specification is either a database or server specification and it cannot be both.
  3. The Audit Action Group is a predefined group of actions within the database engine itself.  (See the MSDN list of Action Groups and Actions)
  4. The Target is essentially where the audit results are sent to, which we have already discussed as a file, the Application Log or the Security Log.

I hope this clarifies some points before we move forward.  Enjoy and stay tuned.

SQL Server Auditing: A Learning Series Part Three

newaudit

Figure 1 – New Audit

Continuing our learning series on Auditing, today we move on to setting up the server audit which will allow us to be able to setup auditing at the instance level.

  1. In SSMS, open the Security node and right-click on Audits and choose New Audit as shown in Figure 1.
  2. This will present us with a default Create Audit dialog box as shown in Figure 2.  Enter a name for your Audit being as descriptive as possible to make it easy for you to look back later and now what this is auditing.
  3. The Queue delay default is 1000 milliseconds.  This is the delay before the audit actions will be processed.
  4. There is a check box if you would like to shut down the server when the audit log fails.  In SQL Server 2012 you have the option to Continue, Shut down the server, or Fail the operation.  Figure 2 is from a SQL Server 2008 server.
  5. As you can see in Figure 2, the default setting for the destination is the file and if this is the setting you choose then you must enter a file path in addition to the other settings shown.  If you choose Security Log or Application Log then all of the file options will be unavailable.
  6. After this process is complete, you will see the audit named under Audits in the Security node.  From there you need to right-click on it and select Enable Audit.
Figure 2 - Create Audit Defaults

Figure 2 – Create Audit Defaults

As with anything in the GUI SSMS, this too can be scripted as an example:

CREATE SERVER AUDIT [Test-Audit] TO SECURITY_LOG WITH (QUEUE_DELAY = 1000)

Enjoy and stay tuned.

SQL Server Audit in SQL Server 2008 R2

Since I am out of the office today I though I would include this fun video from Microsoft to continue with our Auditing theme that we started earlier in the week.  Enjoy!

SQL Server News Hour: SQL Server Audit in SQL Server 2008 R2 – YouTube.

Follow

Get every new post delivered to your Inbox.

Join 1,080 other followers