<?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 index Mcafee HIPS logs? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-index-Mcafee-HIPS-logs/m-p/160499#M32535</link>
    <description>&lt;P&gt;After discovering the event.log was binary-- but the file would seemingly load up fine in notepad, or notepad++.. I discovered the file was actually in a different character set called UCS-2 LE, which according to (&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.1/Admin/Configurecharactersetencoding"&gt;http://docs.splunk.com/Documentation/Splunk/4.1/Admin/Configurecharactersetencoding&lt;/A&gt;) maps to the utf-16le characterset- that I had to specify that in the props.conf on the forwarder.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:ProgramDataMcAfeeHost Intrusion PreventionEvent.log]
index=
disabled = 0
sourcetype = hipsfw
followTail = 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in props.conf (still on forwarder)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[hipsfw]
NO_BINARY_CHECK = true
CHARSET = utf-16le
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Mon, 02 Nov 2015 11:58:41 GMT</pubDate>
    <dc:creator>daniel_goolsby_</dc:creator>
    <dc:date>2015-11-02T11:58:41Z</dc:date>
    <item>
      <title>How to index Mcafee HIPS logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-index-Mcafee-HIPS-logs/m-p/160498#M32534</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;

&lt;P&gt;Mcafee HIPS logs are written on all laptops and basically contain firewall like data. The issue is HIPS logs are written in unicode text format which Splunk sees as a binary file. Has anyone had any success in trying to index hips logs into splunk? &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 26 Feb 2015 15:55:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-index-Mcafee-HIPS-logs/m-p/160498#M32534</guid>
      <dc:creator>theouhuios</dc:creator>
      <dc:date>2015-02-26T15:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to index Mcafee HIPS logs?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-index-Mcafee-HIPS-logs/m-p/160499#M32535</link>
      <description>&lt;P&gt;After discovering the event.log was binary-- but the file would seemingly load up fine in notepad, or notepad++.. I discovered the file was actually in a different character set called UCS-2 LE, which according to (&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.1/Admin/Configurecharactersetencoding"&gt;http://docs.splunk.com/Documentation/Splunk/4.1/Admin/Configurecharactersetencoding&lt;/A&gt;) maps to the utf-16le characterset- that I had to specify that in the props.conf on the forwarder.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[monitor://C:ProgramDataMcAfeeHost Intrusion PreventionEvent.log]
index=
disabled = 0
sourcetype = hipsfw
followTail = 1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;in props.conf (still on forwarder)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[hipsfw]
NO_BINARY_CHECK = true
CHARSET = utf-16le
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 02 Nov 2015 11:58:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-index-Mcafee-HIPS-logs/m-p/160499#M32535</guid>
      <dc:creator>daniel_goolsby_</dc:creator>
      <dc:date>2015-11-02T11:58:41Z</dc:date>
    </item>
  </channel>
</rss>

