<?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 How to monitor Windows failed log on in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49481#M6997</link>
    <description>&lt;P&gt;How to check Windows failed log on using Splunk. &lt;/P&gt;</description>
    <pubDate>Mon, 04 Mar 2013 06:50:56 GMT</pubDate>
    <dc:creator>catch_mili</dc:creator>
    <dc:date>2013-03-04T06:50:56Z</dc:date>
    <item>
      <title>How to monitor Windows failed log on</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49481#M6997</link>
      <description>&lt;P&gt;How to check Windows failed log on using Splunk. &lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2013 06:50:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49481#M6997</guid>
      <dc:creator>catch_mili</dc:creator>
      <dc:date>2013-03-04T06:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor Windows failed log on</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49482#M6998</link>
      <description>&lt;P&gt;The Windows and Active Directory apps (NOTE: Choose relevant app based on your requirement) have a heap of field extractions and eventtypes that will be useful to you for this sort of stuff.&lt;/P&gt;

&lt;P&gt;Assuming your logs are already in Splunk, your search would be as simple as: &lt;/P&gt;

&lt;P&gt;eventtype=windows_logon_failure&lt;/P&gt;

&lt;P&gt;If you don't have the apps installed or dont want to install them you could search for the relevant EventCodes instead. Example below, where "source_of_your_logs" = whatever the source is called in your Splunk installation.&lt;/P&gt;

&lt;P&gt;source=source_of_your_logs EventCode=529 OR EventCode=4625&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2013 07:22:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49482#M6998</guid>
      <dc:creator>mbenwell</dc:creator>
      <dc:date>2013-03-04T07:22:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor Windows failed log on</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49483#M6999</link>
      <description>&lt;P&gt;Further, I would like to monitor files &amp;amp; folders created under C:\ &amp;amp; D:\ drive. &lt;/P&gt;

&lt;P&gt;How can I do that.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2013 09:32:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/How-to-monitor-Windows-failed-log-on/m-p/49483#M6999</guid>
      <dc:creator>catch_mili</dc:creator>
      <dc:date>2013-03-05T09:32:28Z</dc:date>
    </item>
  </channel>
</rss>

