<?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: Why the logs coming from Splunk to Alienvault SIEM sensor, are not readable? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448179#M95425</link>
    <description>&lt;P&gt;How are you sending data to AlienVault?&lt;/P&gt;</description>
    <pubDate>Mon, 18 Mar 2019 17:41:43 GMT</pubDate>
    <dc:creator>nickhills</dc:creator>
    <dc:date>2019-03-18T17:41:43Z</dc:date>
    <item>
      <title>Why the logs coming from Splunk to Alienvault SIEM sensor, are not readable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448176#M95422</link>
      <description>&lt;P&gt;&lt;STRONG&gt;These are the logs coming from splunk to my alienvault SIEM Sensor but my SIEM is unable to read those logs. I have checked all the confs like props.conf, transform.conf, input.conf, output.conf but I couldn't understand the issue. The main issue is in each key value pair in logs, value is being #015#012 this kind of weird. All events are from Windows. At first I thought there may be data Anonymizing  but there is not **TRANSFORMS-annonymize&lt;/STRONG&gt; entry in props.conf. Please help, Thanks in advanced.** &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Mar 17 23:00:03 172.16.8.145  TEC-R90M6PGD Type=NetworkAdapter#015#012Name="Microsoft Wi-Fi Direct Virtual Adapter #2"#015#012Manufacturer="Microsoft"#015#012ProductName="Microsoft Wi-Fi Direct Virtual Adapter"#015#012Status=""#015#012MACAddress="36:F3:9A:3D:28:1D"Mar 17 23:00:02 172.16.8.145  TECSRVTP-DB01 20190317230049.310381#015#012CurrentDiskQueueLength=0#015#012DiskBytesPersec=0#015#012Name=1 G:#015#012PercentDiskReadTime=0#015#012PercentDiskTime=0#015#012PercentDiskWriteTime=0#015#012wmi_type=LocalPhysicalDisk#015#012#015

Mar 17 23:00:02 172.16.8.145  TECSRVTP-DB01 20190317230049.310381#015#012CurrentDiskQueueLength=0#015#012DiskBytesPersec=0#015#012Name=2 F:#015#012PercentDiskReadTime=0#015#012PercentDiskTime=0#015#012PercentDiskWriteTime=0#015#012wmi_type=LocalPhysicalDisk#015#012#015

Mar 17 23:00:02 172.16.8.145  TECSRVEXMBX02 20190317230049.314638#015#012CurrentDiskQueueLength=0#015#012DiskBytesPersec=0#015#012Name=3 F:#015#012PercentDiskReadTime=0#015#012PercentDiskTime=0#015#012PercentDiskWriteTime=0#015#012wmi_type=LocalPhysicalDisk#015#012#015
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 18 Mar 2019 13:28:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448176#M95422</guid>
      <dc:creator>ginstinct</dc:creator>
      <dc:date>2019-03-18T13:28:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why the logs coming from Splunk to Alienvault SIEM sensor, are not readable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448177#M95423</link>
      <description>&lt;P&gt;This looks like a slightly odd encoding/escaping of octal &lt;CODE&gt;\015 \012&lt;/CODE&gt; which is the same as &lt;CODE&gt;\r\n&lt;/CODE&gt; ( and &lt;CODE&gt;\0&lt;/CODE&gt; which is &lt;CODE&gt;null&lt;/CODE&gt;)&lt;BR /&gt;
I would rewrite both &lt;CODE&gt;#0#015#012&lt;/CODE&gt; and &lt;CODE&gt;#015#012&lt;/CODE&gt; as a literal space as you ingest the data.&lt;/P&gt;

&lt;P&gt;Edit: I read this question as if it was AlienVault -&amp;gt; Splunk instead of the other way round, but hopefully the explanation still stands.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 16:44:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448177#M95423</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2019-03-18T16:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why the logs coming from Splunk to Alienvault SIEM sensor, are not readable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448178#M95424</link>
      <description>&lt;P&gt;Thank for your explanation @nickhillscpl , but what should be the workaround to this issue.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 17:39:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448178#M95424</guid>
      <dc:creator>ginstinct</dc:creator>
      <dc:date>2019-03-18T17:39:11Z</dc:date>
    </item>
    <item>
      <title>Re: Why the logs coming from Splunk to Alienvault SIEM sensor, are not readable?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448179#M95425</link>
      <description>&lt;P&gt;How are you sending data to AlienVault?&lt;/P&gt;</description>
      <pubDate>Mon, 18 Mar 2019 17:41:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-the-logs-coming-from-Splunk-to-Alienvault-SIEM-sensor-are/m-p/448179#M95425</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2019-03-18T17:41:43Z</dc:date>
    </item>
  </channel>
</rss>

