<?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 Username Generalization Playbook in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/username-generalization-playbook/m-p/1253551#M397</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hey all, i'm hoping that someone has already started something like this and can get me a few steps past the starting line but as we know, in a corporate environment, there are various ways that usernames come across (abc123, first.last, domain/abc123, domain/first.last, fqdn....etc) from different log sources. This creates complexity for playbooks and manual effort to try and keep up with what log source sends it across in what way.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Does anyone have a playbook started that would generalize them? endgoal would be to generalize it based on what our enterprise username format is and remove any of the junk on either side of it based on whatever the log source sent through. I'm not real versed in creating playbooks yet so any help would be appreciated.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Assuming this works out well, we'd like to expand out and generalize other things like hostname and who knows what else would be benefical.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 06 May 2026 19:53:49 GMT</pubDate>
    <dc:creator>B.Jones279846</dc:creator>
    <dc:date>2026-05-06T19:53:49Z</dc:date>
    <item>
      <title>Username Generalization Playbook</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/username-generalization-playbook/m-p/1253551#M397</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hey all, i'm hoping that someone has already started something like this and can get me a few steps past the starting line but as we know, in a corporate environment, there are various ways that usernames come across (abc123, first.last, domain/abc123, domain/first.last, fqdn....etc) from different log sources. This creates complexity for playbooks and manual effort to try and keep up with what log source sends it across in what way.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Does anyone have a playbook started that would generalize them? endgoal would be to generalize it based on what our enterprise username format is and remove any of the junk on either side of it based on whatever the log source sent through. I'm not real versed in creating playbooks yet so any help would be appreciated.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Assuming this works out well, we'd like to expand out and generalize other things like hostname and who knows what else would be benefical.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2026 19:53:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/username-generalization-playbook/m-p/1253551#M397</guid>
      <dc:creator>B.Jones279846</dc:creator>
      <dc:date>2026-05-06T19:53:49Z</dc:date>
    </item>
  </channel>
</rss>

