<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk App Active Directory - 2008 R2, Advanced Audit Policy in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36050#M1591</link>
    <description>&lt;P&gt;Follow-up:&lt;/P&gt;

&lt;P&gt;Suspecting an auditing issue on the DCs, I did some testing.&lt;/P&gt;

&lt;P&gt;Logged off with my user account.&lt;/P&gt;

&lt;P&gt;Tried to login with a bad username (TESTFAIL)&lt;/P&gt;

&lt;P&gt;Tried to login with a good username and a BAD password&lt;/P&gt;

&lt;P&gt;Logged in successfully&lt;/P&gt;

&lt;P&gt;On the client device I see all the auditing correctly, 4634 for the logoff and 4625s for the failed login attempts. I then check the (2) Domain Controllers to see if I can find corresponding events, I looked by type and just at the general time in which I did this test, and I am not seeing anything.&lt;/P&gt;

&lt;P&gt;Why aren't these audits captured on the DCs?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Aug 2013 17:08:46 GMT</pubDate>
    <dc:creator>boeing_smithbj</dc:creator>
    <dc:date>2013-08-15T17:08:46Z</dc:date>
    <item>
      <title>Splunk App Active Directory - 2008 R2, Advanced Audit Policy</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36049#M1590</link>
      <description>&lt;P&gt;I've got a default setup of Splunk (v 5.0.3) with the following:&lt;BR /&gt;
Active Directory App. (1.2.1)&lt;BR /&gt;
Sideview Utils (2.6.3)&lt;BR /&gt;
SA-ldapsearch (1.1.9)&lt;BR /&gt;
TA for Windows (4.6.3)&lt;BR /&gt;
Universal Forwarder (5.0.3)&lt;/P&gt;

&lt;P&gt;Everything appears to be working correctly - I am seeing log data sent to the indexer from two active directory/dns servers and I can pull up data on all of the menus within the app (security, change management, health, etc.) however... I am having problems finding specific events. I don't know if this is related to how we have our audit policies setup (Advanced Audit Policy, 2008 R2 domain) but suspect it is related.&lt;/P&gt;

&lt;P&gt;Specifically, I am not seeing failed login attempts to the domain when a user is mistyping their passwords on a client workstation. I am seeing this type of event when an admin attempts a remote desktop to one of the Domain Controllers and fails.&lt;/P&gt;

&lt;P&gt;Also, (most likely related to above) I am trying to use the "User Utilization" menu option and filter for a specific time period, but again, I am only seeing events showing up from users connecting directly to a DC (Admin/remote desktop) and not the client connections.&lt;/P&gt;

&lt;P&gt;Any ideas here? Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2013 15:31:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36049#M1590</guid>
      <dc:creator>boeing_smithbj</dc:creator>
      <dc:date>2013-08-15T15:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk App Active Directory - 2008 R2, Advanced Audit Policy</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36050#M1591</link>
      <description>&lt;P&gt;Follow-up:&lt;/P&gt;

&lt;P&gt;Suspecting an auditing issue on the DCs, I did some testing.&lt;/P&gt;

&lt;P&gt;Logged off with my user account.&lt;/P&gt;

&lt;P&gt;Tried to login with a bad username (TESTFAIL)&lt;/P&gt;

&lt;P&gt;Tried to login with a good username and a BAD password&lt;/P&gt;

&lt;P&gt;Logged in successfully&lt;/P&gt;

&lt;P&gt;On the client device I see all the auditing correctly, 4634 for the logoff and 4625s for the failed login attempts. I then check the (2) Domain Controllers to see if I can find corresponding events, I looked by type and just at the general time in which I did this test, and I am not seeing anything.&lt;/P&gt;

&lt;P&gt;Why aren't these audits captured on the DCs?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2013 17:08:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36050#M1591</guid>
      <dc:creator>boeing_smithbj</dc:creator>
      <dc:date>2013-08-15T17:08:46Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk App Active Directory - 2008 R2, Advanced Audit Policy</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36051#M1592</link>
      <description>&lt;P&gt;Figured this out...&lt;/P&gt;

&lt;P&gt;Basically, if you are using the Advanced Audit Configuration settings, you have to enable "Audit Kerberos Authentication Service" under Advanced Audit Configuration &amp;gt; Account Logon.&lt;/P&gt;

&lt;P&gt;With this auditing enabled the Splunk App for Active Directory will begin picking up the following eventIDs from the Domain Controllers:&lt;/P&gt;

&lt;P&gt;4768 – A Kerberos authentication ticket (TGT) was requested – In my test this was a BAD/UNKNOWN username&lt;/P&gt;

&lt;P&gt;4771 – Kerberos pre-authentication failed – In my test this was a good username and BAD password&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2013 20:26:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-Active-Directory-2008-R2-Advanced-Audit-Policy/m-p/36051#M1592</guid>
      <dc:creator>boeing_smithbj</dc:creator>
      <dc:date>2013-08-15T20:26:58Z</dc:date>
    </item>
  </channel>
</rss>

