<?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 Policy scoping by partial endpoint_name --&amp;gt; Endpoint Group in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231452#M8401</link>
    <description>&lt;P&gt;We are doing a pretty rushed XDR rollout, and I need to be able to scope my policies fairly specifically. First idea is to use the 4th character of the endpoint_name (hostname) which is P for Prod, T for Test. But I cannot see a way to use the Endpt Grp filters "wildcard" syntax to do this. I have found some community posts and docs referencing XDR's ability to use regex or regex-ish functionality but I have not got that to work in that filter field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The other idea which might work is to use an XQL query to get a list, and then *perhaps* use that list to add tags, since tags are available as a way to filter Endpoint Groups. Right now I can spell XQL if you spot me a couple letters, so that seems like a longer path. And one thing I'm short of is 'long'.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestion and help are appreciated!&lt;/P&gt;</description>
    <pubDate>Tue, 10 Jun 2025 19:30:18 GMT</pubDate>
    <dc:creator>ptrivino1</dc:creator>
    <dc:date>2025-06-10T19:30:18Z</dc:date>
    <item>
      <title>Policy scoping by partial endpoint_name --&gt; Endpoint Group</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231452#M8401</link>
      <description>&lt;P&gt;We are doing a pretty rushed XDR rollout, and I need to be able to scope my policies fairly specifically. First idea is to use the 4th character of the endpoint_name (hostname) which is P for Prod, T for Test. But I cannot see a way to use the Endpt Grp filters "wildcard" syntax to do this. I have found some community posts and docs referencing XDR's ability to use regex or regex-ish functionality but I have not got that to work in that filter field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The other idea which might work is to use an XQL query to get a list, and then *perhaps* use that list to add tags, since tags are available as a way to filter Endpoint Groups. Right now I can spell XQL if you spot me a couple letters, so that seems like a longer path. And one thing I'm short of is 'long'.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestion and help are appreciated!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jun 2025 19:30:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231452#M8401</guid>
      <dc:creator>ptrivino1</dc:creator>
      <dc:date>2025-06-10T19:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Policy scoping by partial endpoint_name --&gt; Endpoint Group</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231525#M8412</link>
      <description>&lt;P&gt;Hi&amp;nbsp;ptrivino1,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is currently no native way to match a character at a specific position (e.g., 4th character) in endpoint_name using just the endpoints dataset filter. Considering only operators available are contains, not contains, = , !=&lt;BR /&gt;You need to export complete list of endpoints and use filter in Excel sheet&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution". Thank you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Luis&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 11:01:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231525#M8412</guid>
      <dc:creator>eluis</dc:creator>
      <dc:date>2025-06-11T11:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: Policy scoping by partial endpoint_name --&gt; Endpoint Group</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231531#M8414</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/239623"&gt;@ptrivino1&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is a simple query to extract the fourth character while ignoring dashes if found, also added another field "Group Status" for more convenient classification&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;dataset = xdr_data 
| filter agent_hostname != null
| fields agent_hostname 
| alter fouth_letter_array = regextract(agent_hostname , "(?i)(?:[^A-Za-z]*[A-Za-z]){3}[^A-Za-z]*([A-Za-z])")
| alter fourth_letter = arrayindex(fouth_letter_array,0)
| alter Group_Status = 
    if(fourth_letter ="P",  "Prod", 
       fourth_letter ="T",  "Test", // add more 
       fourth_letter)  // return as is if no match
| fields agent_hostname, Group_Status &lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 15:14:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231531#M8414</guid>
      <dc:creator>A.Elzedy</dc:creator>
      <dc:date>2025-06-11T15:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: Policy scoping by partial endpoint_name --&gt; Endpoint Group</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231535#M8416</link>
      <description>&lt;P&gt;also you might want to consider leveraging api capabilities, depending on how critical is grouping for you organization&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM-REST-API/Make-your-first-API-call" target="_blank"&gt;https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM-REST-API/Make-your-first-API-call&lt;/A&gt;&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 15:57:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231535#M8416</guid>
      <dc:creator>A.Elzedy</dc:creator>
      <dc:date>2025-06-11T15:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: Policy scoping by partial endpoint_name --&gt; Endpoint Group</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231675#M8424</link>
      <description>&lt;P&gt;Thank you, that's what I ended up doing.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2025 03:04:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/policy-scoping-by-partial-endpoint-name-gt-endpoint-group/m-p/1231675#M8424</guid>
      <dc:creator>ptrivino1</dc:creator>
      <dc:date>2025-06-13T03:04:58Z</dc:date>
    </item>
  </channel>
</rss>

