<?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 Repost: Assign different Label with different use case within the same Asset in Splunk SOAR</title>
    <link>https://community.splunk.com/t5/Splunk-SOAR/Repost-Assign-different-Label-with-different-use-case-within-the/m-p/754677#M1810</link>
    <description>&lt;P&gt;Hello SOARians,&lt;/P&gt;&lt;P&gt;I am thinking of a scenario where an external alert from a SIEM like qRadar or Elastic should trigger a playbook. For example, a bruteforce alert should trigger a bruteforce playbook, a portscan alert should trigger a portscan playbook, and so on. Unfortunately, it is only possible to assign the same labels to all incoming SIEM alerts. Based on these labels a playbook is then executed.&lt;/P&gt;&lt;P&gt;Is there any way to assign the labels based on the type (e.g. a field of the alarm) of the incoming alarm or to solve the difference between alarms in another way?&lt;/P&gt;</description>
    <pubDate>Fri, 24 Oct 2025 01:02:48 GMT</pubDate>
    <dc:creator>AliMaher</dc:creator>
    <dc:date>2025-10-24T01:02:48Z</dc:date>
    <item>
      <title>Repost: Assign different Label with different use case within the same Asset</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/Repost-Assign-different-Label-with-different-use-case-within-the/m-p/754677#M1810</link>
      <description>&lt;P&gt;Hello SOARians,&lt;/P&gt;&lt;P&gt;I am thinking of a scenario where an external alert from a SIEM like qRadar or Elastic should trigger a playbook. For example, a bruteforce alert should trigger a bruteforce playbook, a portscan alert should trigger a portscan playbook, and so on. Unfortunately, it is only possible to assign the same labels to all incoming SIEM alerts. Based on these labels a playbook is then executed.&lt;/P&gt;&lt;P&gt;Is there any way to assign the labels based on the type (e.g. a field of the alarm) of the incoming alarm or to solve the difference between alarms in another way?&lt;/P&gt;</description>
      <pubDate>Fri, 24 Oct 2025 01:02:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/Repost-Assign-different-Label-with-different-use-case-within-the/m-p/754677#M1810</guid>
      <dc:creator>AliMaher</dc:creator>
      <dc:date>2025-10-24T01:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: Repost: Assign different Label with different use case within the same Asset</title>
      <link>https://community.splunk.com/t5/Splunk-SOAR/Repost-Assign-different-Label-with-different-use-case-within-the/m-p/754681#M1811</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/268583"&gt;@AliMaher&lt;/a&gt;&amp;nbsp;if you can't create a different label at the creation and time the container in SOAR is created, then the next best approach would be to have a "Landing Playbook" that all the alerts come into and are then sent down the correct path.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;This can be done either by simply connecting the right playbook to the output of a decision, or you can switch the label on the container which will then call the associated active playbook(s) that are set to use that label.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- Happy SOARing! If this helped please leave some karma. If it resolved the issue please mark as a solution for others to see. --&lt;/P&gt;</description>
      <pubDate>Fri, 24 Oct 2025 07:13:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-SOAR/Repost-Assign-different-Label-with-different-use-case-within-the/m-p/754681#M1811</guid>
      <dc:creator>phanTom</dc:creator>
      <dc:date>2025-10-24T07:13:43Z</dc:date>
    </item>
  </channel>
</rss>

