<?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: Trendmicro Regex Help in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262143#M189748</link>
    <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Fri, 25 Mar 2016 23:49:56 GMT</pubDate>
    <dc:creator>CYBR_AH</dc:creator>
    <dc:date>2016-03-25T23:49:56Z</dc:date>
    <item>
      <title>Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262139#M189744</link>
      <description>&lt;P&gt;Hi Community,&lt;/P&gt;

&lt;P&gt;I'm trying to figure out how to get the signature and signature id to their own fields. This has been a tricky one for me. Here is part of the _raw event:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|Trend Micro|Deep Security Agent|0.0.0000|0|Invalid Traversal|
|Trend Micro|Deep Security Agent|0.0.0000|0000000|SSL Request|
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;After Deep Security Agent, there is the agent version. After the agent version is the signature ID, then finally the signature. The signature ID seems to range from a single digit number to 7 digits. &lt;/P&gt;

&lt;P&gt;I'd like to be able to get the after everything after the agent version "\d.\d.\d{0,4}" and the pipe to end on the last character of the signature before the other pipe  while also breaking up the signature ID field and signature field. &lt;/P&gt;

&lt;P&gt;Any help would be great and much appreciated. &lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 22:57:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262139#M189744</guid>
      <dc:creator>CYBR_AH</dc:creator>
      <dc:date>2016-03-25T22:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262140#M189745</link>
      <description>&lt;P&gt;If you entire event is separated by &lt;CODE&gt;|&lt;/CODE&gt; characters you should look at the csv sourcetype for automatic field extraction. Otherwise I am assuming that the string &lt;CODE&gt;|Trend Micro|Deep Security Agent|0.0.0000|0|Invalid Traversal|&lt;/CODE&gt; occurs at the start of the line. &lt;/P&gt;

&lt;P&gt;Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;your search&amp;gt; ... | rex field=_raw "^(?:.*?\K\|){4}(?&amp;lt;signature_id&amp;gt;[^\|]+)\|(?&amp;lt;signature&amp;gt;[^\|]+)"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I highly recommend this website for regex help: &lt;A href="https://regex101.com/"&gt;https://regex101.com/&lt;/A&gt;&lt;BR /&gt;
Also the specific solution here came from perlmonks : &lt;A href="http://www.perlmonks.org/?node_id=721801"&gt;http://www.perlmonks.org/?node_id=721801&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 23:20:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262140#M189745</guid>
      <dc:creator>jplumsdaine22</dc:creator>
      <dc:date>2016-03-25T23:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262141#M189746</link>
      <description>&lt;P&gt;Like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | rex "(?:[\|][^\|]*){3}\|(?&amp;lt;SignatureID&amp;gt;[^\|]*)\|(?&amp;lt;Signature&amp;gt;[^\|]*)"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 25 Mar 2016 23:34:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262141#M189746</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-03-25T23:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262142#M189747</link>
      <description>&lt;P&gt;Thank you this also worked!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 23:49:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262142#M189747</guid>
      <dc:creator>CYBR_AH</dc:creator>
      <dc:date>2016-03-25T23:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262143#M189748</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 23:49:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262143#M189748</guid>
      <dc:creator>CYBR_AH</dc:creator>
      <dc:date>2016-03-25T23:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262144#M189749</link>
      <description>&lt;P&gt;This regex also looks more efficient than mine - you should probably accept this answer instead.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 00:12:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262144#M189749</guid>
      <dc:creator>jplumsdaine22</dc:creator>
      <dc:date>2016-03-26T00:12:46Z</dc:date>
    </item>
    <item>
      <title>Re: Trendmicro Regex Help</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262145#M189750</link>
      <description>&lt;P&gt;Ok I will. I wish I could accept both. &lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2016 00:14:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trendmicro-Regex-Help/m-p/262145#M189750</guid>
      <dc:creator>CYBR_AH</dc:creator>
      <dc:date>2016-03-26T00:14:47Z</dc:date>
    </item>
  </channel>
</rss>

