Having been working on Splunk for the last few days, one of my last hurdles was to easily monitor, present and alert on Active Directory events such as account lock outs, group changes etc. Low and behold Splunk has an app called Splunk App for Microsoft Windows Active Directory – problem solved! Well as Lee Corso would say – “Not so fast my friend!”
The documentation for the Splunk App for AD starts with a warning, that its complicated to install…meh they just want PS revenue right? The documentation starts off straight forward, mostly configuring your audit policies to log relevant information but ends up in a twisty turvey rabbit hole of horror! So much so, that the sales rep even suggested I use another app! So, here is how to actually monitor AD events, not using the Splunk App for AD.
The app you should look at, of course if it meets all of your requirements, is the Windows Security Operations Center app. This app is not available for direct install from the app market directly from Splunk, you will need to download it. Also it should be noted that as of this writing its only certified to work Splunk 5, however I am testing it with Splunk 6 and having only a few minor problems that I suspect are related to my audit policy versus the application not working. In my limited test environment, its generating just under 100MB per day (about 75 user accounts and tests scenarios like adding/removing/deleting accounts from the domain admins group). For purposes of this walk through, I’ll assume you have a central Splunk server already installed and the Universal Forwarder installed on your Domain Controller(s).
- In my test environment, I have configured a Group Policy for my domain controllers for Audit Policy to log success and failure of all defined events (logon, account management, policy change, privilege use, and system events).
- Download the Windows Security Operations Center app from http://apps.splunk.com/app/647/
- Log into Splunk and click on the Manage Apps button
- Click Install app from file and browse the location you saved the file in the first step and click Upload.
- Click Set up now
- If you have used the default installation and configuration as we’ve done in the Using Splunk to Monitor Windows Event Logs post, then leave index and sourcetype at their defaults and click Save.
- If you return to the dashboard you’ll now see the Windows Security Operations dashboard, click on the Login events menu in the dashboard and click Active Directory unsuccessful logins. If you have had any, you should now see those events.
- As I navigate through the other menus, I am also seeing data related to new accounts (if you recall we created an account for Splunk to read AD accounts for authentication), accounts I’ve unlocked and software I’ve installed (the Splunk UniversalForwarder specifically).
The Windows Security Operations Center App for Splunk is an easy to install and configure app, unlike the official Splunk App. If you have a need to monitor AD events, this app should come in handy. Of course at the end of the day its still Splunk, so if you can find it in your event log, you can find it in Splunk.