<?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 custom status update for notable event using phantom playbook in Splunk SOAR</title>
    <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395874#M47</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I have to update the notable event status using phantom. But the status are custom created ones , not the default status available in splunk app for phantom so its is throwing error in playbook "invalid status"&lt;/P&gt;
&lt;P&gt;Can any one have a suggestion here to update the custom status.&lt;/P&gt;</description>
    <pubDate>Sun, 07 Jun 2020 17:46:15 GMT</pubDate>
    <dc:creator>kvswathi</dc:creator>
    <dc:date>2020-06-07T17:46:15Z</dc:date>
    <item>
      <title>custom status update for notable event using phantom playbook</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395874#M47</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I have to update the notable event status using phantom. But the status are custom created ones , not the default status available in splunk app for phantom so its is throwing error in playbook "invalid status"&lt;/P&gt;
&lt;P&gt;Can any one have a suggestion here to update the custom status.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Jun 2020 17:46:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395874#M47</guid>
      <dc:creator>kvswathi</dc:creator>
      <dc:date>2020-06-07T17:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: custom status update for notable event using phantom playbook</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395875#M48</link>
      <description>&lt;P&gt;This is not yet supported but a feature request is in place (at the time of this writing).&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2019 15:57:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395875#M48</guid>
      <dc:creator>sam_splunk</dc:creator>
      <dc:date>2019-08-26T15:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: custom status update for notable event using phantom playbook</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395876#M49</link>
      <description>&lt;P&gt;Thank you for the update&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 05:26:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395876#M49</guid>
      <dc:creator>kvswathi</dc:creator>
      <dc:date>2019-08-27T05:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: custom status update for notable event using phantom playbook</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395877#M50</link>
      <description>&lt;P&gt;The HTTP App for Phantom can be used to perform a POST request to the Splunk ES API to change the status of a Notable Event to any custom status you may have defined:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://my.phantom.us/4.5/docs/app_reference/phantom_http#post-data" target="_blank"&gt;https://my.phantom.us/4.5/docs/app_reference/phantom_http#post-data&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/ES/5.3.0/API/NotableEventAPIreference" target="_blank"&gt;https://docs.splunk.com/Documentation/ES/5.3.0/API/NotableEventAPIreference&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;You will want to use the ID value of the custom status defined in revewstatuses.conf:&lt;/P&gt;

&lt;P&gt;"A status ID matching a status in reviewstatuses.conf. Only required if you are changing the status of the event."&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:00:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395877#M50</guid>
      <dc:creator>cblumer_splunk</dc:creator>
      <dc:date>2020-09-30T02:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: custom status update for notable event using phantom playbook</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395878#M51</link>
      <description>&lt;P&gt;Since the feature is not implemented yet, you can use the below query to update custom status for the notable in Splunk from Phantom.&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;| makeresults | eval rule_id="&amp;lt;id&amp;gt;", status="&amp;lt;custom status&amp;gt;", comment="&amp;lt;enter comment here&amp;gt;",  owner="&amp;lt;owner name&amp;gt;",  user="&amp;lt;owner name&amp;gt;" , event_id="&amp;lt;id&amp;gt;", time="&amp;lt;time&amp;gt;" , rule_name="&amp;lt;rule name&amp;gt;", urgency="&amp;lt;urgency&amp;gt;"| table comment event_id owner rule_id rule_name status time urgency user | outputlookup append=true  incident_review_lookup&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2019 07:35:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/custom-status-update-for-notable-event-using-phantom-playbook/m-p/395878#M51</guid>
      <dc:creator>ansusabu</dc:creator>
      <dc:date>2019-10-31T07:35:31Z</dc:date>
    </item>
  </channel>
</rss>

