<?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 Assign Risk in Correlation Search in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424913#M5407</link>
    <description>&lt;P&gt;We are trying to integrate the risk analysis framework in our incident response process.  &lt;/P&gt;

&lt;P&gt;We have developed a library of correlation searches where the results produce multiple objects upon which we need to assign risk, e.g. src, dest, users.  When we and the "| sendalert risk" components to the correlation searches, notable events no longer generate and risk scores are NOT applied.  When we run the searches as ad-hoc, the risk scores are properly assigned and the results appear as expected.&lt;/P&gt;

&lt;P&gt;Can "| sendalert" not appear in a correlation search?   The Risk Analysis Adaptive response action is not sufficient, as we can not dynamically set the risk tolerance, nor set risk against multiple objects with that action. &lt;/P&gt;

&lt;P&gt;e.g: &lt;CODE&gt;| eval risk_score=case(severity=="critical", 20,  severity=="high", 15, severity=="medium", 10, severity=="low", 5&lt;/CODE&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Aug 2018 14:51:12 GMT</pubDate>
    <dc:creator>panovattack</dc:creator>
    <dc:date>2018-08-23T14:51:12Z</dc:date>
    <item>
      <title>Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424913#M5407</link>
      <description>&lt;P&gt;We are trying to integrate the risk analysis framework in our incident response process.  &lt;/P&gt;

&lt;P&gt;We have developed a library of correlation searches where the results produce multiple objects upon which we need to assign risk, e.g. src, dest, users.  When we and the "| sendalert risk" components to the correlation searches, notable events no longer generate and risk scores are NOT applied.  When we run the searches as ad-hoc, the risk scores are properly assigned and the results appear as expected.&lt;/P&gt;

&lt;P&gt;Can "| sendalert" not appear in a correlation search?   The Risk Analysis Adaptive response action is not sufficient, as we can not dynamically set the risk tolerance, nor set risk against multiple objects with that action. &lt;/P&gt;

&lt;P&gt;e.g: &lt;CODE&gt;| eval risk_score=case(severity=="critical", 20,  severity=="high", 15, severity=="medium", 10, severity=="low", 5&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Aug 2018 14:51:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424913#M5407</guid>
      <dc:creator>panovattack</dc:creator>
      <dc:date>2018-08-23T14:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424914#M5408</link>
      <description>&lt;P&gt;Just an update that we are waiting for a Splunk and ES upgrade to see if  that fixes the issue.  We'd like to be able to dynamically assign risk to multiple objects in a single correlation search. &lt;/P&gt;</description>
      <pubDate>Wed, 26 Sep 2018 18:24:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424914#M5408</guid>
      <dc:creator>panovattack</dc:creator>
      <dc:date>2018-09-26T18:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424915#M5409</link>
      <description>&lt;P&gt;Still can't seem to figure it out after upgrade.  Is there anyway to reliably assign risk to multiple objects from a correlation search or a saved search?  Or is the limit one?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Nov 2018 20:01:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424915#M5409</guid>
      <dc:creator>panovattack</dc:creator>
      <dc:date>2018-11-13T20:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424916#M5410</link>
      <description>&lt;P&gt;See &lt;A href="https://answers.splunk.com/answers/594711/splunk-enterprise-security-how-can-i-configure-a-c.html"&gt;https://answers.splunk.com/answers/594711/splunk-enterprise-security-how-can-i-configure-a-c.html&lt;/A&gt; and &lt;A href="http://dev.splunk.com/view/enterprise-security/SP-CAAAFBD"&gt;http://dev.splunk.com/view/enterprise-security/SP-CAAAFBD&lt;/A&gt; to learn how to add risk to multiple objects.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Nov 2018 20:38:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424916#M5410</guid>
      <dc:creator>smoir_splunk</dc:creator>
      <dc:date>2018-11-13T20:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424917#M5411</link>
      <description>&lt;P&gt;The approach here does not seem to work when it comes to a correlation search.   Multiple | sendalerts work in ad-hoc, but not when run as part of a correlation search. &lt;/P&gt;</description>
      <pubDate>Tue, 13 Nov 2018 21:14:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424917#M5411</guid>
      <dc:creator>panovattack</dc:creator>
      <dc:date>2018-11-13T21:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424918#M5412</link>
      <description>&lt;P&gt;There are these examples in docs:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/ES/5.2.0/User/RiskScoring"&gt;http://docs.splunk.com/Documentation/ES/5.2.0/User/RiskScoring&lt;/A&gt;&lt;BR /&gt;
The &lt;CODE&gt;appendpipe&lt;/CODE&gt; option is pretty good, but that said multiple &lt;CODE&gt;| sendalert&lt;/CODE&gt;s should be supported as well - what version of ES are you on?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Dec 2018 20:22:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424918#M5412</guid>
      <dc:creator>kchamplin_splun</dc:creator>
      <dc:date>2018-12-04T20:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: Assign Risk in Correlation Search</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424919#M5413</link>
      <description>&lt;P&gt;I'm adding a score to several objects from one event from a saved search&lt;/P&gt;

&lt;P&gt;I do this&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| eval risk_object=mvappend(field_1."|system",field_2."|user",field_3."|user",field_4."|other")
| eval risk_score=1
| mvexpand risk_object
| eval x=split(risk_object, "|")
| eval risk_object=mvindex(x, 0, 0), risk_object_type=mvindex(x,1,1)
| fields - x
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and then sendalert at the end, so for each event, I get 4 events.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2019 04:16:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Assign-Risk-in-Correlation-Search/m-p/424919#M5413</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2019-10-01T04:16:06Z</dc:date>
    </item>
  </channel>
</rss>

