<?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 Re: Limit User-ID Agent queries to cerain Windows event-IDs in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/limit-user-id-agent-queries-to-cerain-windows-event-ids/m-p/1242569#M6484</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208972"&gt;@SBegass&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I don't believe that it's possible to exclude certain event IDs that your agent can read. There's two common scenarios that you'll see for this issue, and that's either building your rulebase with the potential of seeing this admin account recognized or simply excluding those user IDs so you don't see them.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Nov 2025 14:49:13 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2025-11-25T14:49:13Z</dc:date>
    <item>
      <title>Limit User-ID Agent queries to cerain Windows event-IDs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/limit-user-id-agent-queries-to-cerain-windows-event-ids/m-p/1242217#M6467</link>
      <description>&lt;P&gt;We have been using PA-User-ID Agent for years an it was working fine. The Agent is connecting to Domain-Controller Log and maps user-name and ip-address of successful logins for firewall-policy usage.&lt;/P&gt;
&lt;P&gt;Yesterday we changed GPOs on the Domain Controller to enable Kerberos-Ticket Logging and since then we received unwanted mappings: A user starting a RDP Session to a Server and logging on to the server with a different user-name (i.e. Tier-1 Admin). Then the local pc-ip address is mapped to the server-username and thus the local user to ip-mapping is beeing overwritten.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to excempt certain Windows event-IDs (i.e. ID4768) from beeing queried, or explicitly setting the desired event-IDs for querying?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Nov 2025 13:26:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/limit-user-id-agent-queries-to-cerain-windows-event-ids/m-p/1242217#M6467</guid>
      <dc:creator>SBegass</dc:creator>
      <dc:date>2025-11-19T13:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: Limit User-ID Agent queries to cerain Windows event-IDs</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/limit-user-id-agent-queries-to-cerain-windows-event-ids/m-p/1242569#M6484</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208972"&gt;@SBegass&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I don't believe that it's possible to exclude certain event IDs that your agent can read. There's two common scenarios that you'll see for this issue, and that's either building your rulebase with the potential of seeing this admin account recognized or simply excluding those user IDs so you don't see them.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Nov 2025 14:49:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/limit-user-id-agent-queries-to-cerain-windows-event-ids/m-p/1242569#M6484</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2025-11-25T14:49:13Z</dc:date>
    </item>
  </channel>
</rss>

