<?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: Programatically  setting severity within a search in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102500#M182978</link>
    <description>&lt;P&gt;I think you can manually set the severity field from within the correlation search (field name is "severity"). I would approach this by performing your lookup for known malicious domains and if true then set the severity to critical.&lt;/P&gt;

&lt;P&gt;Something like might work:&lt;/P&gt;

&lt;P&gt;...|lookup nasty_ip_list ip OUTPUT ip as nasty_ip|eval severity=if(len(nasty_ip)&amp;gt;0,"critical","medium")|...&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 10:11:45 GMT</pubDate>
    <dc:creator>sheamus69</dc:creator>
    <dc:date>2020-09-29T10:11:45Z</dc:date>
    <item>
      <title>Programatically  setting severity within a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102498#M182976</link>
      <description>&lt;P&gt;I am writing a search that will track when the firewall sees outbound traffic over non-standard ports.  I have a requirement that states if the destination ip is a known malicious domain, then the severity should be critical.  Otherwise, it will be medium.  I can certainly accomplish this by writing two searches (one for malicious domains, one for non-malicious domains), but was wondering if I could do it within one search. &lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2013 20:11:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102498#M182976</guid>
      <dc:creator>iisaphd</dc:creator>
      <dc:date>2013-10-16T20:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Programatically  setting severity within a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102499#M182977</link>
      <description>&lt;P&gt;You should look at the append or join command.&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/SearchReference/Append"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/SearchReference/Append&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
or&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/SearchReference/Join"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/SearchReference/Join&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;
Another option would be to provide cleaned but representative search results that you want to combine.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2013 20:46:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102499#M182977</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-10-16T20:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: Programatically  setting severity within a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102500#M182978</link>
      <description>&lt;P&gt;I think you can manually set the severity field from within the correlation search (field name is "severity"). I would approach this by performing your lookup for known malicious domains and if true then set the severity to critical.&lt;/P&gt;

&lt;P&gt;Something like might work:&lt;/P&gt;

&lt;P&gt;...|lookup nasty_ip_list ip OUTPUT ip as nasty_ip|eval severity=if(len(nasty_ip)&amp;gt;0,"critical","medium")|...&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:11:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Programatically-setting-severity-within-a-search/m-p/102500#M182978</guid>
      <dc:creator>sheamus69</dc:creator>
      <dc:date>2020-09-29T10:11:45Z</dc:date>
    </item>
  </channel>
</rss>

