<?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 and Splunk Add-On for Windows in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427600#M5472</link>
    <description>&lt;P&gt;is there a question here?&lt;BR /&gt;
what is the version of the windows TA you are using?&lt;BR /&gt;
iirc, the 5.0 version has those bugs and it says somewhere in the docs to go back to 4.8.4&lt;/P&gt;</description>
    <pubDate>Tue, 11 Dec 2018 01:42:42 GMT</pubDate>
    <dc:creator>adonio</dc:creator>
    <dc:date>2018-12-11T01:42:42Z</dc:date>
    <item>
      <title>Splunk Enterprise Security and Splunk Add-On for Windows</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427599#M5471</link>
      <description>&lt;P&gt;As best as I can tell there is a bug between the Splunk Enterprise Security App and Splunk Add-On for Windows.  The Splunk Enterprise Security App Windows Event Log Cleared looks for sourcetype=wineventlog:security.  However the Splunk Add-On for Windows props file that renames wineventlog:security back to wineventlog causing the Windows Event Log Cleared to never fire.&lt;/P&gt;

&lt;P&gt;Additionally, the transform regex may be wrong, not sure, could not get it to fire as written so I created a custom transform, (?m)^LogName=(\S+).&lt;/P&gt;</description>
      <pubDate>Mon, 10 Dec 2018 20:16:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427599#M5471</guid>
      <dc:creator>jeburkes76</dc:creator>
      <dc:date>2018-12-10T20:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security and Splunk Add-On for Windows</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427600#M5472</link>
      <description>&lt;P&gt;is there a question here?&lt;BR /&gt;
what is the version of the windows TA you are using?&lt;BR /&gt;
iirc, the 5.0 version has those bugs and it says somewhere in the docs to go back to 4.8.4&lt;/P&gt;</description>
      <pubDate>Tue, 11 Dec 2018 01:42:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427600#M5472</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2018-12-11T01:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security and Splunk Add-On for Windows</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427601#M5473</link>
      <description>&lt;P&gt;I guess sort of a question, I am new to transforms and props configuration files so it was a sanity check. Maybe my team and I made a mistake and installed a later version of the Add-On for Microsoft version 5.0.1 but we believe it came with ES 5.20 when we installed hence our confusion and concern if it is a known issue.  This is a test environment so maybe we missed something.  Thanks for the info.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Dec 2018 12:38:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Splunk-Enterprise-Security-and-Splunk-Add-On-for-Windows/m-p/427601#M5473</guid>
      <dc:creator>jeburkes76</dc:creator>
      <dc:date>2018-12-14T12:38:34Z</dc:date>
    </item>
  </channel>
</rss>

