<?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: Device Onboarding in Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Onboard-a-device-in-Splunk/m-p/655113#M111013</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/243225"&gt;@debjit_k&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;the&amp;nbsp;&lt;SPAN&gt;sangfor&amp;nbsp;firewall hasn't an Add-On on Splunkbase, so you need to create a CIM 4.X compliant new one.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There are two different approaches to Add-Ons:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;create different add-ons for the roles: one for the input and one for parsing,&lt;/LI&gt;&lt;LI&gt;use the same Add-On for all roles,&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I usually prefer the second one.&lt;/P&gt;&lt;P&gt;In the Add-On you have to put:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;the inputs.conf file to ingest the files that, I suppose, you receive using an rsyslog or syslog-ng server,&lt;/LI&gt;&lt;LI&gt;the props.conf file to contain all the parsing options (props.conf, transforms.conf)&lt;/LI&gt;&lt;LI&gt;all the CIM compliance transformations (eventtypes.conf, tags.conf, props.conf, transofrma.conf and eventually lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;To create a CIM 4.x compliant Add-On you can use the Add-On Builder App (&lt;A href="https://splunkbase.splunk.com/app/2962" target="_blank"&gt;https://splunkbase.splunk.com/app/2962&lt;/A&gt;) or using an App like SA-cim_vladiator (&lt;A href="https://splunkbase.splunk.com/app/2968" target="_blank"&gt;https://splunkbase.splunk.com/app/2968&lt;/A&gt;) to identify the transformation requested.&lt;/P&gt;&lt;P&gt;You could use the second one for Add-On definitions and the first one for CIM 4.x compliance checks.&lt;/P&gt;&lt;P&gt;In few words you have:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;to extract all the fields required (here you can find the required and the optional fields for each DataModel&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/CIM/5.1.1/User/Howtousethesereferencetables" target="_blank"&gt;https://docs.splunk.com/Documentation/CIM/5.1.1/User/Howtousethesereferencetables&lt;/A&gt;&amp;nbsp;),&lt;/LI&gt;&lt;LI&gt;to normalize field names creating aliases for your field names,&lt;/LI&gt;&lt;LI&gt;to normalize some field values (e.g. for the action field you must use the following values: success, failure, pending, error,&lt;/LI&gt;&lt;LI&gt;eventually add lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Tue, 22 Aug 2023 06:48:43 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2023-08-22T06:48:43Z</dc:date>
    <item>
      <title>How to Onboard a device in Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Onboard-a-device-in-Splunk/m-p/655101#M111011</link>
      <description>&lt;P&gt;Hi All,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I wanted to onboard new device in Spunk which is sangfor firewall my question is how can I onboard it so that it also became a CIM compliant&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My basic understand is&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Team will configure syslog to sent logs to our syslog&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From syslog -&amp;gt; UF -&amp;gt; IDX -&amp;gt; SH&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe in idx I need to define the input.conf file for new FW now my question is does sangfor has any add-on (like paloalto which curve the data itself in proper name tag everything) if it has Can anyone please help me with the link and where I need to install this addon in search head or idx or UF to make my data CIM compliant.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 20:23:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-Onboard-a-device-in-Splunk/m-p/655101#M111011</guid>
      <dc:creator>debjit_k</dc:creator>
      <dc:date>2023-08-22T20:23:06Z</dc:date>
    </item>
    <item>
      <title>Re: Device Onboarding in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Onboard-a-device-in-Splunk/m-p/655113#M111013</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/243225"&gt;@debjit_k&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;the&amp;nbsp;&lt;SPAN&gt;sangfor&amp;nbsp;firewall hasn't an Add-On on Splunkbase, so you need to create a CIM 4.X compliant new one.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There are two different approaches to Add-Ons:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;create different add-ons for the roles: one for the input and one for parsing,&lt;/LI&gt;&lt;LI&gt;use the same Add-On for all roles,&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I usually prefer the second one.&lt;/P&gt;&lt;P&gt;In the Add-On you have to put:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;the inputs.conf file to ingest the files that, I suppose, you receive using an rsyslog or syslog-ng server,&lt;/LI&gt;&lt;LI&gt;the props.conf file to contain all the parsing options (props.conf, transforms.conf)&lt;/LI&gt;&lt;LI&gt;all the CIM compliance transformations (eventtypes.conf, tags.conf, props.conf, transofrma.conf and eventually lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;To create a CIM 4.x compliant Add-On you can use the Add-On Builder App (&lt;A href="https://splunkbase.splunk.com/app/2962" target="_blank"&gt;https://splunkbase.splunk.com/app/2962&lt;/A&gt;) or using an App like SA-cim_vladiator (&lt;A href="https://splunkbase.splunk.com/app/2968" target="_blank"&gt;https://splunkbase.splunk.com/app/2968&lt;/A&gt;) to identify the transformation requested.&lt;/P&gt;&lt;P&gt;You could use the second one for Add-On definitions and the first one for CIM 4.x compliance checks.&lt;/P&gt;&lt;P&gt;In few words you have:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;to extract all the fields required (here you can find the required and the optional fields for each DataModel&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/CIM/5.1.1/User/Howtousethesereferencetables" target="_blank"&gt;https://docs.splunk.com/Documentation/CIM/5.1.1/User/Howtousethesereferencetables&lt;/A&gt;&amp;nbsp;),&lt;/LI&gt;&lt;LI&gt;to normalize field names creating aliases for your field names,&lt;/LI&gt;&lt;LI&gt;to normalize some field values (e.g. for the action field you must use the following values: success, failure, pending, error,&lt;/LI&gt;&lt;LI&gt;eventually add lookups.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 22 Aug 2023 06:48:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-Onboard-a-device-in-Splunk/m-p/655113#M111013</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2023-08-22T06:48:43Z</dc:date>
    </item>
  </channel>
</rss>

