<?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 Enterprise Security: What is the best practice for collecting Windows logs? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-What-is-the-best-practice-for/m-p/203618#M1102</link>
    <description>&lt;P&gt;The best practice for the collection of logs for use with Enterprise Security is to use (or build) an add-on that is compatible with the Splunk Common Information Model. One of the default filters on &lt;A href="https://splunkbase.splunk.com/apps/#/search/windows/cim/4.6,4.5,4.4,4.3,4.2,4.1,4.0,3.0"&gt;splunkbase&lt;/A&gt; is CIM compatibility. The &lt;A href="https://splunkbase.splunk.com/app/742"&gt;Splunk Add-on for Microsoft Windows&lt;/A&gt; is CIM compatible, and will provide the eventtype and tagging requirements for the typical Windows Event Log sources. If you've already been ingesting Windows logs using that add-on, then you should have the log sources tagged properly for use with the CIM data models. Confirm that your Windows Event Log data is showing up in a datamodel (Example: review the Authentication data model using Pivot,) and if it's there you can move on to defining use-cases.&lt;/P&gt;

&lt;P&gt;In a security environment, all data is relevant. So begin by defining the critical use-cases in your environment, and what data is required to fulfill those use-cases. Scope the data sources to CIM datamodels. To see which add-ons populate a given datamodel, use the 2 searches documented in this &lt;A href="http://blogs.splunk.com/2015/05/01/relating-add-ons-to-cim/"&gt;blog post&lt;/A&gt;. If you are working with correlation searches, review the search to see which datamodels are referenced. &lt;/P&gt;

&lt;P&gt;With the list of required use-cases, and the knowledge of what data you need to fulfill those use-cases, you can choose to mark data sources that are less important to your current priorities and temporarily exclude them from collection. &lt;/P&gt;</description>
    <pubDate>Wed, 05 Oct 2016 22:08:59 GMT</pubDate>
    <dc:creator>ekost</dc:creator>
    <dc:date>2016-10-05T22:08:59Z</dc:date>
    <item>
      <title>Splunk Enterprise Security: What is the best practice for collecting Windows logs?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-What-is-the-best-practice-for/m-p/203617#M1101</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;

&lt;P&gt;We are collecting all logs from Windows (wineventlogs, windows, perfmon) from all the Domain Controllers. It's a huge amount of logs we are ingesting. What is the best practice to get the logs which has value for Splunk Enterprise Security and what logs are to be excluded? &lt;/P&gt;</description>
      <pubDate>Tue, 20 Sep 2016 14:54:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-What-is-the-best-practice-for/m-p/203617#M1101</guid>
      <dc:creator>kiran331</dc:creator>
      <dc:date>2016-09-20T14:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security: What is the best practice for collecting Windows logs?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-What-is-the-best-practice-for/m-p/203618#M1102</link>
      <description>&lt;P&gt;The best practice for the collection of logs for use with Enterprise Security is to use (or build) an add-on that is compatible with the Splunk Common Information Model. One of the default filters on &lt;A href="https://splunkbase.splunk.com/apps/#/search/windows/cim/4.6,4.5,4.4,4.3,4.2,4.1,4.0,3.0"&gt;splunkbase&lt;/A&gt; is CIM compatibility. The &lt;A href="https://splunkbase.splunk.com/app/742"&gt;Splunk Add-on for Microsoft Windows&lt;/A&gt; is CIM compatible, and will provide the eventtype and tagging requirements for the typical Windows Event Log sources. If you've already been ingesting Windows logs using that add-on, then you should have the log sources tagged properly for use with the CIM data models. Confirm that your Windows Event Log data is showing up in a datamodel (Example: review the Authentication data model using Pivot,) and if it's there you can move on to defining use-cases.&lt;/P&gt;

&lt;P&gt;In a security environment, all data is relevant. So begin by defining the critical use-cases in your environment, and what data is required to fulfill those use-cases. Scope the data sources to CIM datamodels. To see which add-ons populate a given datamodel, use the 2 searches documented in this &lt;A href="http://blogs.splunk.com/2015/05/01/relating-add-ons-to-cim/"&gt;blog post&lt;/A&gt;. If you are working with correlation searches, review the search to see which datamodels are referenced. &lt;/P&gt;

&lt;P&gt;With the list of required use-cases, and the knowledge of what data you need to fulfill those use-cases, you can choose to mark data sources that are less important to your current priorities and temporarily exclude them from collection. &lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2016 22:08:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-What-is-the-best-practice-for/m-p/203618#M1102</guid>
      <dc:creator>ekost</dc:creator>
      <dc:date>2016-10-05T22:08:59Z</dc:date>
    </item>
  </channel>
</rss>

