<?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: How to track domain logons from DC security logs? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324408#M60392</link>
    <description>&lt;P&gt;Thanks I will experiment with your suggestion!&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2017 19:44:45 GMT</pubDate>
    <dc:creator>johann2017</dc:creator>
    <dc:date>2017-02-28T19:44:45Z</dc:date>
    <item>
      <title>How to track domain logons from DC security logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324406#M60390</link>
      <description>&lt;P&gt;I want to be able to track domain logons from our DC security logs. I am monitoring Event 4624, but the DC security logs only seem to provide domain member authentication for Type 3 logons. What are others using for this?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 21:10:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324406#M60390</guid>
      <dc:creator>johann2017</dc:creator>
      <dc:date>2017-02-23T21:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to track domain logons from DC security logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324407#M60391</link>
      <description>&lt;P&gt;Depends on how homogeneous your network and your user base are.  Check for these and see what you find.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;(EventID=528 OR EventID=540 OR EventID=552 OR EventID=4624 OR EventID=4648)  
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Whether the individual workstations are going to forward their logs of type 7 events, whether you have technical users that will be using runas and generating type 9s, logging on through VPN and generating type 10s, not to mention whether there is any KVM/IP going on and generating pseudo-Type 2s, and so on, is highly organization-specific.  &lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 22:54:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324407#M60391</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-02-23T22:54:25Z</dc:date>
    </item>
    <item>
      <title>Re: How to track domain logons from DC security logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324408#M60392</link>
      <description>&lt;P&gt;Thanks I will experiment with your suggestion!&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 19:44:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324408#M60392</guid>
      <dc:creator>johann2017</dc:creator>
      <dc:date>2017-02-28T19:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to track domain logons from DC security logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324409#M60393</link>
      <description>&lt;P&gt;Oh, and that's for windows; unix logons have a whole different set of criteria.  As a place to start, look for stuff like this - &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;((pam_vas:* AND "&amp;lt;succeeded") OR "Accepted" OR "Auth_methods_completed") 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 28 Feb 2017 20:50:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-track-domain-logons-from-DC-security-logs/m-p/324409#M60393</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-02-28T20:50:51Z</dc:date>
    </item>
  </channel>
</rss>

