<?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: Active directory data input. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32025#M5643</link>
    <description>&lt;P&gt;A good starting point would be the documentation, specifically &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/AuditActiveDirectory" rel="nofollow"&gt;Monitor Active Directory&lt;/A&gt; in the Admin manual.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jan 2011 02:16:16 GMT</pubDate>
    <dc:creator>ftk</dc:creator>
    <dc:date>2011-01-26T02:16:16Z</dc:date>
    <item>
      <title>Active directory data input.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32024#M5642</link>
      <description>&lt;P&gt;What is the most suggested way to pull data from Active Diretory?&lt;/P&gt;

&lt;P&gt;We need to input Active Directory's user information for event co-relations.&lt;/P&gt;

&lt;P&gt;THanks Gurus~!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2011 02:07:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32024#M5642</guid>
      <dc:creator>clyde772</dc:creator>
      <dc:date>2011-01-26T02:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: Active directory data input.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32025#M5643</link>
      <description>&lt;P&gt;A good starting point would be the documentation, specifically &lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/AuditActiveDirectory" rel="nofollow"&gt;Monitor Active Directory&lt;/A&gt; in the Admin manual.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2011 02:16:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32025#M5643</guid>
      <dc:creator>ftk</dc:creator>
      <dc:date>2011-01-26T02:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: Active directory data input.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32026#M5644</link>
      <description>&lt;P&gt;Wow - answering a year old query.&lt;/P&gt;

&lt;P&gt;Set up a temporal lookup based on the Windows Security Log (which you will need to ingest from the domain controllers).  You can use &lt;A href="http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/default.aspx?i=j" target="_blank"&gt;http://www.ultimatewindowssecurity.com/securitylog/encyclopedia/default.aspx?i=j&lt;/A&gt; to figure out the EventCode that you need to read for the user logons.&lt;/P&gt;

&lt;P&gt;Note that most windows systems use Kerberos "pre-authentication" to do authentication.  So the logon events are not necessarily obvious.  Just take a look at the events and extract the username and domain (preferenbly as the CIM compliant fields user and src_nt_domain.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:32:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Active-directory-data-input/m-p/32026#M5644</guid>
      <dc:creator>ahall_splunk</dc:creator>
      <dc:date>2020-09-28T11:32:57Z</dc:date>
    </item>
  </channel>
</rss>

