<?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 Defining a Known User Object List for Automated Playbook Logic in XSOAR in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/defining-a-known-user-object-list-for-automated-playbook-logic/m-p/1243715#M4210</link>
    <description>&lt;P data-start="0" data-end="271"&gt;I need to define a &lt;STRONG data-start="19" data-end="38"&gt;known user list&lt;/STRONG&gt; as an &lt;STRONG data-start="45" data-end="60"&gt;Object List&lt;/STRONG&gt; so that the playbook can automatically check it. If the username involved in the incident is found in this known list, the condition should pass and the incident should move forward toward automatic resolution.&lt;/P&gt;
&lt;P data-start="0" data-end="271"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="273" data-end="444" data-is-last-node="" data-is-only-node=""&gt;How do we properly define a list inside the playbook and configure the logic so that when a username matches an entry in that list, the playbook proceeds to the next step?&lt;/P&gt;</description>
    <pubDate>Thu, 11 Dec 2025 15:07:28 GMT</pubDate>
    <dc:creator>Chamindu</dc:creator>
    <dc:date>2025-12-11T15:07:28Z</dc:date>
    <item>
      <title>Defining a Known User Object List for Automated Playbook Logic in XSOAR</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/defining-a-known-user-object-list-for-automated-playbook-logic/m-p/1243715#M4210</link>
      <description>&lt;P data-start="0" data-end="271"&gt;I need to define a &lt;STRONG data-start="19" data-end="38"&gt;known user list&lt;/STRONG&gt; as an &lt;STRONG data-start="45" data-end="60"&gt;Object List&lt;/STRONG&gt; so that the playbook can automatically check it. If the username involved in the incident is found in this known list, the condition should pass and the incident should move forward toward automatic resolution.&lt;/P&gt;
&lt;P data-start="0" data-end="271"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="273" data-end="444" data-is-last-node="" data-is-only-node=""&gt;How do we properly define a list inside the playbook and configure the logic so that when a username matches an entry in that list, the playbook proceeds to the next step?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Dec 2025 15:07:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/defining-a-known-user-object-list-for-automated-playbook-logic/m-p/1243715#M4210</guid>
      <dc:creator>Chamindu</dc:creator>
      <dc:date>2025-12-11T15:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: Defining a Known User Object List for Automated Playbook Logic in XSOAR</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/defining-a-known-user-object-list-for-automated-playbook-logic/m-p/1244701#M4216</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hi&lt;/STRONG&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There are &lt;STRONG&gt;multiple&lt;/STRONG&gt; options for achieving your goal - automated close of specific user related incidents.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*&lt;STRONG&gt;NOTE&lt;/STRONG&gt;* - personally, &lt;STRONG&gt;i would not recommend&lt;/STRONG&gt; you automatically closing incidents based on usernames only but this part is your call &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. pre-processing rule using the built-in feature:&lt;/P&gt;
&lt;P&gt;Settings-&amp;gt;Object Setup-&amp;gt;Pre-Process Rules-&amp;gt;New Rule button&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&amp;nbsp;This will give you the ability to run transformers (Scripts with transformer tag) on the incident context data and validate username involved. using simple code logic you can return True/False and by that match a filter on when you want to close / ingore the incident&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;2. Playbook Method&lt;/P&gt;
&lt;P&gt;You can create a dynamic list in:&lt;/P&gt;
&lt;P&gt;Settings-&amp;gt;Advanced-&amp;gt;Lists-&amp;gt;Add a list button&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;choose your list type of data (JSON,txt)&lt;/LI&gt;
&lt;LI&gt;add relevant users the the list (if txt has been choosen then use a the list as the following "list like string": Username1, Username2 where comma is your delimiter (similar to python)&lt;/LI&gt;
&lt;LI&gt;use the demisto.executeCommand("getList", {"listName": *listname you used*}) to get the list values&lt;/LI&gt;
&lt;LI&gt;use the demisto.executeCommand("&lt;EM&gt;addToList", {"listName":"", "listData":""}) to add values to the list&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;then - the usage is pretty much up to you - use Condition + transformer code (as suggested above before), playbook tasks (with getList) and contidion etc etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.13/Cortex-XSOAR-Administrator-Guide/Work-With-Lists" target="_blank"&gt;https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/6.13/Cortex-XSOAR-Administrator-Guide/Work-With-Lists&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;feel free to reach again if you need to &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;best of luck!&lt;/P&gt;</description>
      <pubDate>Sun, 28 Dec 2025 07:13:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/defining-a-known-user-object-list-for-automated-playbook-logic/m-p/1244701#M4216</guid>
      <dc:creator>ofmoalem</dc:creator>
      <dc:date>2025-12-28T07:13:03Z</dc:date>
    </item>
  </channel>
</rss>

