<?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 How to create an alias for a CIM field in Splunk ES? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502323#M8872</link>
    <description>&lt;P&gt;I am extracting the src and user values from failed login attempts in Shibboleth logs and the value is "failed" so I can set an event type for failed Shib login attempts.&lt;/P&gt;

&lt;P&gt;When I check the CIM documentation for fields for Authentication event datasets, I see the value ES expects is "failure".&lt;/P&gt;

&lt;P&gt;How do I create an alias for the field action so that "failed" is set to "failure" so ES can then leverage it?&lt;/P&gt;

&lt;P&gt;Thx  &lt;/P&gt;</description>
    <pubDate>Fri, 06 Dec 2019 16:57:17 GMT</pubDate>
    <dc:creator>jwalzerpitt</dc:creator>
    <dc:date>2019-12-06T16:57:17Z</dc:date>
    <item>
      <title>How to create an alias for a CIM field in Splunk ES?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502323#M8872</link>
      <description>&lt;P&gt;I am extracting the src and user values from failed login attempts in Shibboleth logs and the value is "failed" so I can set an event type for failed Shib login attempts.&lt;/P&gt;

&lt;P&gt;When I check the CIM documentation for fields for Authentication event datasets, I see the value ES expects is "failure".&lt;/P&gt;

&lt;P&gt;How do I create an alias for the field action so that "failed" is set to "failure" so ES can then leverage it?&lt;/P&gt;

&lt;P&gt;Thx  &lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2019 16:57:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502323#M8872</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2019-12-06T16:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alias for a CIM field in Splunk ES?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502324#M8873</link>
      <description>&lt;P&gt;Actually digging through Splunk Answers saw a way to use sedcmd and was wondering if this would be a way to handle the issue:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=foo sourcetype="shibboleth:process" "Login by*" failed
| rex mode=sed field=_raw "s/failed/failure/g" 
| rex field=_raw "-\s\[(?P&amp;lt;src&amp;gt;(?:[0-9]{1,3}\.){3}[0-9]{1,3}).*:\sLogin\sby\s'(?P&amp;lt;user&amp;gt;.*)'\s(?P&amp;lt;action&amp;gt;failure)"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Running this extracts all three fields with correct values. If this looks good, could I then create an event type with this search for failed Shib login attempts?&lt;/P&gt;

&lt;P&gt;Thx&lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2019 17:17:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502324#M8873</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2019-12-06T17:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alias for a CIM field in Splunk ES?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502325#M8874</link>
      <description>&lt;P&gt;Would a field alias do the trick? &lt;A href="https://docs.splunk.com/Documentation/CIM/4.14.0/User/UsetheCIMtonormalizeCPUperformancemetrics#Step_5._Make_fields_CIM-compliant_2"&gt;https://docs.splunk.com/Documentation/CIM/4.14.0/User/UsetheCIMtonormalizeCPUperformancemetrics#Step_5._Make_fields_CIM-compliant_2&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2019 17:43:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502325#M8874</guid>
      <dc:creator>lkutch_splunk</dc:creator>
      <dc:date>2019-12-06T17:43:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alias for a CIM field in Splunk ES?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502326#M8875</link>
      <description>&lt;P&gt;Thx for the reply and link to the doc.&lt;/P&gt;

&lt;P&gt;It's not so much the field needs an alias, but the value "failed" needs to be set as "failure". I thought that's where the SEDCMD would come into play. &lt;/P&gt;</description>
      <pubDate>Fri, 06 Dec 2019 17:59:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502326#M8875</guid>
      <dc:creator>jwalzerpitt</dc:creator>
      <dc:date>2019-12-06T17:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alias for a CIM field in Splunk ES?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502327#M8876</link>
      <description>&lt;P&gt;Probably the string &lt;CODE&gt;failed&lt;/CODE&gt; is in your logs and it is a simple field extraction.  If that's the case, then you need to create a &lt;CODE&gt;calculated field&lt;/CODE&gt; that does:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;eval action=if(action=="failed", "failure", action)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 06 Dec 2019 20:20:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/How-to-create-an-alias-for-a-CIM-field-in-Splunk-ES/m-p/502327#M8876</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-12-06T20:20:47Z</dc:date>
    </item>
  </channel>
</rss>

