<?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 Using Elevate Policy for access to Environment Variables? in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424845#M9251</link>
    <description>&lt;P&gt;This is an interesting case don't know if it has been answered before. We have a couple of users who need access to modify their environment variables. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can properly give access to SystemPropertiesAdvanced.exe in Windows/System32. But I was wondering if there was any way to not let the user do other functions in System Properties like: &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Change computer name&lt;/LI&gt;&lt;LI&gt;Alter Start and Recovery settings&lt;/LI&gt;&lt;LI&gt;etc.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anything is appreciated!&lt;/P&gt;</description>
    <pubDate>Wed, 22 Oct 2025 18:30:50 GMT</pubDate>
    <dc:creator>RKuczer</dc:creator>
    <dc:date>2025-10-22T18:30:50Z</dc:date>
    <item>
      <title>Using Elevate Policy for access to Environment Variables?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424845#M9251</link>
      <description>&lt;P&gt;This is an interesting case don't know if it has been answered before. We have a couple of users who need access to modify their environment variables. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can properly give access to SystemPropertiesAdvanced.exe in Windows/System32. But I was wondering if there was any way to not let the user do other functions in System Properties like: &lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Change computer name&lt;/LI&gt;&lt;LI&gt;Alter Start and Recovery settings&lt;/LI&gt;&lt;LI&gt;etc.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anything is appreciated!&lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 18:30:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424845#M9251</guid>
      <dc:creator>RKuczer</dc:creator>
      <dc:date>2025-10-22T18:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: Using Elevate Policy for access to Environment Variables?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424846#M9252</link>
      <description>&lt;P&gt;we personally  have a policy for Environmental variables  - Allowing users the ability to edit the user and system variables currently can be done from cmd or&amp;nbsp;windows + R&amp;nbsp;using the following command rundll32 sysdm.cpl,EditEnvironmentVariables&amp;nbsp; and we actually block SystemPropertiesAdvanced.exe  as you say it gives access to many other things that we don't want our dev/users to have access too. Therefore we actually have a block policy for systempropertiesadvanced.exe and have an allow policy for the above which I believe doesn't require admin rights and can access the user/system ENV buttons. Hope that helps? We then say on the block GUI prompt to use the other method suggested &lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 21:09:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424846#M9252</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-22T21:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Using Elevate Policy for access to Environment Variables?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424847#M9253</link>
      <description>&lt;P&gt;we personally  have a policy for Environmental variables  - Allowing users the ability to edit the user and system variables currently can be done from cmd or&amp;nbsp;windows + R&amp;nbsp;using the following command rundll32 sysdm.cpl,EditEnvironmentVariables&amp;nbsp; and we actually block SystemPropertiesAdvanced.exe  as you say it gives access to many other things that we don't want our dev/users to have access too. Therefore we actually have a block policy for systempropertiesadvanced.exe and have an allow policy for the above which I believe doesn't require admin rights and can access the user/system ENV buttons. Hope that helps? We then say on the block GUI prompt to use the other method suggested &lt;/P&gt;</description>
      <pubDate>Wed, 22 Oct 2025 21:09:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424847#M9253</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-10-22T21:09:13Z</dc:date>
    </item>
    <item>
      <title>Re: Using Elevate Policy for access to Environment Variables?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424848#M9254</link>
      <description>&lt;P&gt;@Touseef-ur rehman​&amp;nbsp;- Thanks this worked great, appreciate the quick help!&lt;/P&gt;&lt;P&gt;=&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2025 17:24:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/using-elevate-policy-for-access-to-environment-variables/m-p/1424848#M9254</guid>
      <dc:creator>RKuczer</dc:creator>
      <dc:date>2025-10-23T17:24:11Z</dc:date>
    </item>
  </channel>
</rss>

