<?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 AD group as target not used correctly in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/ad-group-as-target-not-used-correctly/m-p/1416752#M7924</link>
    <description>&lt;P&gt;We have a privilege management policy that has an AD group as target. Any devices in that group should have this policy active. &lt;/P&gt;&lt;P&gt;We notice lately that apparently the agent is not able to determine group membership and activates this policy event though that device is not a member of that group. A Request Settings or reboot solves the problem, but this situation should not happen. This policy should never be active if the AD group can not be solved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anybody else has this problem?&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jan 2024 12:54:40 GMT</pubDate>
    <dc:creator>john_gordijn</dc:creator>
    <dc:date>2024-01-25T12:54:40Z</dc:date>
    <item>
      <title>AD group as target not used correctly</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/ad-group-as-target-not-used-correctly/m-p/1416752#M7924</link>
      <description>&lt;P&gt;We have a privilege management policy that has an AD group as target. Any devices in that group should have this policy active. &lt;/P&gt;&lt;P&gt;We notice lately that apparently the agent is not able to determine group membership and activates this policy event though that device is not a member of that group. A Request Settings or reboot solves the problem, but this situation should not happen. This policy should never be active if the AD group can not be solved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anybody else has this problem?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 12:54:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/ad-group-as-target-not-used-correctly/m-p/1416752#M7924</guid>
      <dc:creator>john_gordijn</dc:creator>
      <dc:date>2024-01-25T12:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: AD group as target not used correctly</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/ad-group-as-target-not-used-correctly/m-p/1416753#M7925</link>
      <description>&lt;P&gt;There is a Known Issue (bug) that has been around for a while that is related to this. See &lt;A alt="https://community.cyberark.com/s/article/KI00017163" href="https://community.cyberark.com/s/article/KI00017163" target="_blank"&gt;KI#00017163: The policy won't apply if the agent cannot resolve the selected AD group (site.com)&lt;/A&gt;. While that bug indicates that the policy is &lt;B&gt;not &lt;/B&gt;applied if the agent can't resolve the AD group, I would not be surprised if there is more to the bug and it also causes the behaviour you are seeing in some instances. My recommendation to you would be to open a support case providing all the specifics of your issue (including a SupportInfo trace from an impacted agent) but also mention this similar Known Issue article. Hopefully Support can help determine if it's the same bug, this is a new bug, or just something specific to your configuration that can be resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS. I have not personally seen this occur in my setup.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2024 13:56:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/ad-group-as-target-not-used-correctly/m-p/1416753#M7925</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-01-25T13:56:32Z</dc:date>
    </item>
  </channel>
</rss>

