<?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>article Version Specific Application Policies in Endpoint Privilege Manager (EPM) Articles</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/version-specific-application-policies/ta-p/1427595</link>
    <description>&lt;P&gt;When functionality changes between EPM agent releases, you may need to apply different policy logic based on the agent version. This procedure ensures that version-specific behaviors are isolated and prioritized correctly.&lt;/P&gt;
&lt;P&gt;This document defines an approach whereby release-specific application policies can be defined. In this example, the policies are shown to be specific to release 26.2.1. However, the actual “Agent Version” used can be changed depending on the specific upgrade being performed&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 1: Create a Dynamic Endpoint Group&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Endpoints &amp;gt; Endpoint Groups&lt;/STRONG&gt; and click &lt;STRONG&gt;Create Endpoint Group&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Name:&lt;/STRONG&gt; &lt;SPAN style="color: #188038;"&gt;Agents - Version 26.2.1&lt;/SPAN&gt; (Use a descriptive name).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Type:&lt;/STRONG&gt; Select &lt;SPAN style="color: #188038;"&gt;Dynamic&lt;/SPAN&gt;.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Rule Definition:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Property:&lt;/STRONG&gt; Agent Version&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Operator:&lt;/STRONG&gt; &lt;SPAN style="color: #188038;"&gt;Starts With&lt;/SPAN&gt; (Recommended over "Equals" to account for minor build variations).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Value:&lt;/STRONG&gt;&lt;SPAN style="color: #2ecc71;"&gt; &lt;SPAN style="color: #188038;"&gt;26.2.1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 2: Duplicate and Adjust Impacted Policies&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Identify the policy requiring a version-specific change.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Select &lt;STRONG&gt;Duplicate&lt;/STRONG&gt; from the policy actions.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Rename:&lt;/STRONG&gt; Append the version to the name (e.g.,&amp;nbsp;&lt;SPAN style="color: #188038;"&gt;Elevate Developer Tools - v26.2.1&lt;/SPAN&gt;).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Priority:&lt;/STRONG&gt; Increase the priority so this policy is evaluated &lt;STRONG&gt;before&lt;/STRONG&gt; the standard existing policy.&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 3: Target the Policy&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;In the new policy, scroll to the &lt;STRONG&gt;Targets&lt;/STRONG&gt; section.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Add the Dynamic Group created in Step 1.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Important Logic Note:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;P&gt;Targets across different categories (e.g., AD Computer Groups &lt;STRONG&gt;AND&lt;/STRONG&gt; Endpoint Groups) are combined using &lt;STRONG&gt;AND&lt;/STRONG&gt; logic.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Targets within the same category are combined using &lt;STRONG&gt;OR&lt;/STRONG&gt; logic.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;EM&gt;Result:&lt;/EM&gt; The policy will only apply if the computer is in the specified AD Group &lt;STRONG&gt;AND&lt;/STRONG&gt; running the specified Agent Version&lt;/P&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Note: If the "old" policy has a very broad target (like "All Computers"), it is recommended to add the new &lt;STRONG&gt;Version 26.2.1 Dynamic Group&lt;/STRONG&gt; as an &lt;STRONG&gt;Exclusion&lt;/STRONG&gt; in that old policy. This ensures a clear division and prevents an agent from potentially matching both sets of criteria.&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 4: Validate and Roll Out&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Test:&lt;/STRONG&gt; Upgrade a small "Pilot" group of agents to the new version.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Verify:&lt;/STRONG&gt; Use the &lt;STRONG&gt;Policy Audit&lt;/STRONG&gt; on the endpoint to confirm the new version-specific policy is the one being applied.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Cleanup:&lt;/STRONG&gt; Once all agents are eventually upgraded to the new version, you can remove the version-specific policy and remain with the original policy definition.&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Mar 2026 14:06:22 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-03-24T14:06:22Z</dc:date>
    <item>
      <title>Version Specific Application Policies</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/version-specific-application-policies/ta-p/1427595</link>
      <description>&lt;P&gt;When functionality changes between EPM agent releases, you may need to apply different policy logic based on the agent version. This procedure ensures that version-specific behaviors are isolated and prioritized correctly.&lt;/P&gt;
&lt;P&gt;This document defines an approach whereby release-specific application policies can be defined. In this example, the policies are shown to be specific to release 26.2.1. However, the actual “Agent Version” used can be changed depending on the specific upgrade being performed&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 1: Create a Dynamic Endpoint Group&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Navigate to &lt;STRONG&gt;Endpoints &amp;gt; Endpoint Groups&lt;/STRONG&gt; and click &lt;STRONG&gt;Create Endpoint Group&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Name:&lt;/STRONG&gt; &lt;SPAN style="color: #188038;"&gt;Agents - Version 26.2.1&lt;/SPAN&gt; (Use a descriptive name).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Type:&lt;/STRONG&gt; Select &lt;SPAN style="color: #188038;"&gt;Dynamic&lt;/SPAN&gt;.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Rule Definition:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Property:&lt;/STRONG&gt; Agent Version&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Operator:&lt;/STRONG&gt; &lt;SPAN style="color: #188038;"&gt;Starts With&lt;/SPAN&gt; (Recommended over "Equals" to account for minor build variations).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Value:&lt;/STRONG&gt;&lt;SPAN style="color: #2ecc71;"&gt; &lt;SPAN style="color: #188038;"&gt;26.2.1&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 2: Duplicate and Adjust Impacted Policies&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;Identify the policy requiring a version-specific change.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Select &lt;STRONG&gt;Duplicate&lt;/STRONG&gt; from the policy actions.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Rename:&lt;/STRONG&gt; Append the version to the name (e.g.,&amp;nbsp;&lt;SPAN style="color: #188038;"&gt;Elevate Developer Tools - v26.2.1&lt;/SPAN&gt;).&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Priority:&lt;/STRONG&gt; Increase the priority so this policy is evaluated &lt;STRONG&gt;before&lt;/STRONG&gt; the standard existing policy.&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 3: Target the Policy&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;In the new policy, scroll to the &lt;STRONG&gt;Targets&lt;/STRONG&gt; section.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Add the Dynamic Group created in Step 1.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Important Logic Note:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;&lt;LI&gt;
&lt;P&gt;Targets across different categories (e.g., AD Computer Groups &lt;STRONG&gt;AND&lt;/STRONG&gt; Endpoint Groups) are combined using &lt;STRONG&gt;AND&lt;/STRONG&gt; logic.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;Targets within the same category are combined using &lt;STRONG&gt;OR&lt;/STRONG&gt; logic.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;EM&gt;Result:&lt;/EM&gt; The policy will only apply if the computer is in the specified AD Group &lt;STRONG&gt;AND&lt;/STRONG&gt; running the specified Agent Version&lt;/P&gt;
&lt;/LI&gt;&lt;/UL&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;Note: If the "old" policy has a very broad target (like "All Computers"), it is recommended to add the new &lt;STRONG&gt;Version 26.2.1 Dynamic Group&lt;/STRONG&gt; as an &lt;STRONG&gt;Exclusion&lt;/STRONG&gt; in that old policy. This ensures a clear division and prevents an agent from potentially matching both sets of criteria.&lt;/P&gt;
&lt;H2&gt;&lt;STRONG&gt;Step 4: Validate and Roll Out&lt;/STRONG&gt;&lt;/H2&gt;
&lt;OL&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Test:&lt;/STRONG&gt; Upgrade a small "Pilot" group of agents to the new version.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Verify:&lt;/STRONG&gt; Use the &lt;STRONG&gt;Policy Audit&lt;/STRONG&gt; on the endpoint to confirm the new version-specific policy is the one being applied.&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Cleanup:&lt;/STRONG&gt; Once all agents are eventually upgraded to the new version, you can remove the version-specific policy and remain with the original policy definition.&lt;/P&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 14:06:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/version-specific-application-policies/ta-p/1427595</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-03-24T14:06:22Z</dc:date>
    </item>
  </channel>
</rss>

