<?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 Splunk Addon for Unix cannot decode auditd logs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Addon-for-Unix-cannot-decode-auditd-logs/m-p/694910#M115443</link>
    <description>&lt;P&gt;Good day,&lt;/P&gt;&lt;P&gt;I have installed Splunk ES v9.2.1 on a Linux server (CentOS 7.9). On Splunk ES server, I have installed Splunk Addon for Unix and Linux with all scripts including rlog.sh enabled. I have also configured Splunk Forwarder v9.2.1 a Linux client (CentOS-7.9). Splunk ES server is receiving logs from client as per normal. But I still have a problem with auditd logs coming from client. The USER_CMD part of auditd logs still appear as HEX format, instead of ASCII.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, part of the log reads&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;USER_CMD=636174202F6574632F736861646F77&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;where I expect a decoded value to be ASCII as in:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;USER_CMD=cat /etc/shadow&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;What am I doing wrong? And what can I do to view auditd logs in Splunk without me as an analyst decode each log entry one at a time?&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2024 20:31:55 GMT</pubDate>
    <dc:creator>NatSec</dc:creator>
    <dc:date>2024-07-31T20:31:55Z</dc:date>
    <item>
      <title>Splunk Addon for Unix cannot decode auditd logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Addon-for-Unix-cannot-decode-auditd-logs/m-p/694910#M115443</link>
      <description>&lt;P&gt;Good day,&lt;/P&gt;&lt;P&gt;I have installed Splunk ES v9.2.1 on a Linux server (CentOS 7.9). On Splunk ES server, I have installed Splunk Addon for Unix and Linux with all scripts including rlog.sh enabled. I have also configured Splunk Forwarder v9.2.1 a Linux client (CentOS-7.9). Splunk ES server is receiving logs from client as per normal. But I still have a problem with auditd logs coming from client. The USER_CMD part of auditd logs still appear as HEX format, instead of ASCII.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For example, part of the log reads&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;USER_CMD=636174202F6574632F736861646F77&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;where I expect a decoded value to be ASCII as in:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;USER_CMD=cat /etc/shadow&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;BR /&gt;What am I doing wrong? And what can I do to view auditd logs in Splunk without me as an analyst decode each log entry one at a time?&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2024 20:31:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Addon-for-Unix-cannot-decode-auditd-logs/m-p/694910#M115443</guid>
      <dc:creator>NatSec</dc:creator>
      <dc:date>2024-07-31T20:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Addon for Unix cannot decode auditd logs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-Addon-for-Unix-cannot-decode-auditd-logs/m-p/694914#M115444</link>
      <description>&lt;P&gt;I'm not 100% sure it will help but TA_nix is not meant for auditd logs. There are at least two different add-ons on splunkbase specifically for auditd logs.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2024 21:23:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-Addon-for-Unix-cannot-decode-auditd-logs/m-p/694914#M115444</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-07-31T21:23:33Z</dc:date>
    </item>
  </channel>
</rss>

