<?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: Administration tasks block in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419119#M9057</link>
    <description>&lt;P&gt;Generally speaking the OS prevents actions that require elevation and you use EPM to specific the processes/applications you want to elevate. The rest are blocked just by the nature of a user not having the permissions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to take a least privilege approach and only grant what you want them to do instead of a sweeping policy that allows lots of things and then trying to block those things you dont want.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create advanced policy for windows, elevate, then change the drop down to administrative tasks and allow only what you want. &lt;/P&gt;</description>
    <pubDate>Tue, 13 May 2025 18:26:44 GMT</pubDate>
    <dc:creator>phornat</dc:creator>
    <dc:date>2025-05-13T18:26:44Z</dc:date>
    <item>
      <title>Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419118#M9056</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Admionistrations tasks refer to the main tasks that a user can perform to administrate its PC. It is possible to create Elevate policy to let users to perform in elevate mode some tasks. It is possible to have same policies but to block some admin task?&lt;/P&gt;&lt;P&gt;When I want to create a Block policy Admin tasks cannot be selected. Is there a reason?&lt;/P&gt;&lt;P&gt;How to proceed to created Admin tasks Block policies? Can you share any guidelines?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 15:45:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419118#M9056</guid>
      <dc:creator>Faab</dc:creator>
      <dc:date>2025-05-13T15:45:15Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419119#M9057</link>
      <description>&lt;P&gt;Generally speaking the OS prevents actions that require elevation and you use EPM to specific the processes/applications you want to elevate. The rest are blocked just by the nature of a user not having the permissions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try to take a least privilege approach and only grant what you want them to do instead of a sweeping policy that allows lots of things and then trying to block those things you dont want.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create advanced policy for windows, elevate, then change the drop down to administrative tasks and allow only what you want. &lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 18:26:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419119#M9057</guid>
      <dc:creator>phornat</dc:creator>
      <dc:date>2025-05-13T18:26:44Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419120#M9058</link>
      <description>&lt;P&gt;You shouldnt need to block any of that if you dont give them permission to do it in the first place. Hope that makes sense.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 18:27:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419120#M9058</guid>
      <dc:creator>phornat</dc:creator>
      <dc:date>2025-05-13T18:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419121#M9059</link>
      <description>&lt;P&gt;I'd recommend watching some of the videos and training here took me several viewings and create the administrative tasks from the link below you need to scroll down - &lt;A alt="https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center" href="https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center" target="_blank"&gt;https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center&lt;/A&gt; loads of training material here spotlight videos and office hour vids very good. \&lt;/P&gt;&lt;P&gt;We allow at least Diskpart this way and via a policy creation mind you so users can shrink their WSL2 sessions as they get too big for example. Pretty sure we have ticked a few others too&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Below I believe is accurate ...&lt;/P&gt;&lt;P&gt;CyberArk EPM allows you to create Elevate policies for Windows administrative tasks, enabling users to perform specific admin actions in elevated mode. The list of supported administrative tasks for Allow and Elevate policies is documented, including tasks like System Remote Desktop, Disk Management, Group Policy Editor, and more&amp;nbsp;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;&lt;B&gt;Windows administrative tasks&lt;/B&gt;&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;However, the knowledge sources do not mention the ability to directly create Block policies for these predefined Windows administrative tasks. When creating a Block policy, administrative tasks cannot be selected as a group or predefined set—this appears to be a product limitation, as only Allow and Elevate actions are supported for these tasks.&lt;/P&gt;&lt;P&gt;&lt;B&gt;Guidelines:&lt;/B&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If you need to block specific administrative actions, you may need to define custom application definitions targeting the executables or commands associated with those tasks, rather than using the predefined "administrative tasks" group.&lt;/LI&gt;&lt;LI&gt;The documentation does not provide explicit steps or support for blocking the entire set of administrative tasks as a group.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In summary, blocking predefined administrative tasks as a group is not supported in EPM; you must target specific executables or actions individually in your Block policies. If you require more granular control, consider defining custom application definitions for the tasks you wish to block&amp;nbsp;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;&lt;B&gt;Windows policies&lt;/B&gt;&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;&lt;B&gt;Windows administrative tasks&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;Windows policies&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;&lt;B&gt;Create a policy&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;Windows policies&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To manually block Windows processes and services that users typically use when they had admin rights, you need to create **Block policies** in CyberArk EPM targeting the specific executables and services associated with administrative actions. Here’s how you can proceed, based on the available documentation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 1. Block Windows Processes (Executables) not obviously administrative tasks &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Create an advanced policy**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;1. In the EPM management console, go to **Policies**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;2. Select **Application policies** and click **Create advanced policy**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;3. Set the **Action** to **Block** and the **Platform** to **Windows**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;4. Under **Scope**, click **Add definition**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;5. Set the **Definition type** to **Executable**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;6. For each process you want to block (e.g., `cmd.exe`, `powershell.exe`, `taskmgr.exe`, etc.), set:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Original filename**: is exactly `cmd.exe` (or the relevant process)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Publisher's signature**: starts with `Microsoft`&lt;/P&gt;&lt;P&gt;&amp;nbsp;7. Repeat for each process you want to block.&lt;/P&gt;&lt;P&gt;&amp;nbsp;8. Under **Targets**, select the computers, AD groups, and users this policy should apply to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;9. Click **Create** to activate the policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Example from the documentation:**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To block processes like `cmd.exe`, `powershell.exe`, and `taskmgr.exe` (often used for admin tasks), you can define each as an executable in your Block policy scope [Create a new advanced policy to block Winlogon](&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon" href="https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon" target="_blank"&gt;https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 2. Block Access to Windows Services&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Block the Services Management Console**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Create a Block policy for `services.exe`:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- **Filename**: is exactly `services.exe`&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- **Original filename**: is exactly `SERVICES.EXE`&lt;/P&gt;&lt;P&gt;&amp;nbsp;- This will prevent users from launching the Services management console [Community answer](&lt;A alt="https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4" href="https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4" target="_blank"&gt;https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Restrict Service Access via User Policy**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Go to **Policies** &amp;gt; **User policies** &amp;gt; **Create user policy**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Set **Type** to **Services access**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Details &amp;gt; User permissions**, select **No access**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Scope**, add the specific service (e.g., `Spooler` for the Print Spooler).&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Targets**, select the relevant users/computers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Click **Create** [Prevent users from modifying the print spooler service](&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice" href="https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice" target="_blank"&gt;https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 3. General Guidance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- You must define each process or service you want to block individually, as EPM does not support blocking all administrative tasks as a group.&lt;/P&gt;&lt;P&gt;- Common admin tools to consider blocking: `cmd.exe`, `powershell.exe`, `taskmgr.exe`, `regedit.exe`, `mmc.exe`, `services.exe`, and others as needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Note:** Always test your policies in a controlled environment before deploying broadly to avoid accidentally blocking legitimate business processes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you need to block additional tools or scripts, repeat the process for each relevant executable or service.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 18:30:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419121#M9059</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-13T18:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419122#M9060</link>
      <description>&lt;P&gt;I'd recommend watching some of the videos and training here took me several viewings and create the administrative tasks from the link below you need to scroll down - &lt;A alt="https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center" href="https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center" target="_blank"&gt;https://community.cyberark.com/s/group/0F92J0000000QwvSAE/epm-admin-resource-center&lt;/A&gt; loads of training material here spotlight videos and office hour vids very good. \&lt;/P&gt;&lt;P&gt;We allow at least Diskpart this way and via a policy creation mind you so users can shrink their WSL2 sessions as they get too big for example. Pretty sure we have ticked a few others too&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Below I believe is accurate ...&lt;/P&gt;&lt;P&gt;CyberArk EPM allows you to create Elevate policies for Windows administrative tasks, enabling users to perform specific admin actions in elevated mode. The list of supported administrative tasks for Allow and Elevate policies is documented, including tasks like System Remote Desktop, Disk Management, Group Policy Editor, and more&amp;nbsp;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;&lt;B&gt;Windows administrative tasks&lt;/B&gt;&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;However, the knowledge sources do not mention the ability to directly create Block policies for these predefined Windows administrative tasks. When creating a Block policy, administrative tasks cannot be selected as a group or predefined set—this appears to be a product limitation, as only Allow and Elevate actions are supported for these tasks.&lt;/P&gt;&lt;P&gt;&lt;B&gt;Guidelines:&lt;/B&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If you need to block specific administrative actions, you may need to define custom application definitions targeting the executables or commands associated with those tasks, rather than using the predefined "administrative tasks" group.&lt;/LI&gt;&lt;LI&gt;The documentation does not provide explicit steps or support for blocking the entire set of administrative tasks as a group.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In summary, blocking predefined administrative tasks as a group is not supported in EPM; you must target specific executables or actions individually in your Block policies. If you require more granular control, consider defining custom application definitions for the tasks you wish to block&amp;nbsp;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;&lt;B&gt;Windows policies&lt;/B&gt;&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;&lt;B&gt;Windows administrative tasks&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Windowsadministrativetasks" target="_blank"&gt;Windows policies&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;&lt;B&gt;Create a policy&lt;/B&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" href="https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Createapolicy" target="_blank"&gt;Windows policies&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To manually block Windows processes and services that users typically use when they had admin rights, you need to create **Block policies** in CyberArk EPM targeting the specific executables and services associated with administrative actions. Here’s how you can proceed, based on the available documentation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 1. Block Windows Processes (Executables) not obviously administrative tasks &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Create an advanced policy**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;1. In the EPM management console, go to **Policies**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;2. Select **Application policies** and click **Create advanced policy**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;3. Set the **Action** to **Block** and the **Platform** to **Windows**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;4. Under **Scope**, click **Add definition**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;5. Set the **Definition type** to **Executable**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;6. For each process you want to block (e.g., `cmd.exe`, `powershell.exe`, `taskmgr.exe`, etc.), set:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Original filename**: is exactly `cmd.exe` (or the relevant process)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;- **Publisher's signature**: starts with `Microsoft`&lt;/P&gt;&lt;P&gt;&amp;nbsp;7. Repeat for each process you want to block.&lt;/P&gt;&lt;P&gt;&amp;nbsp;8. Under **Targets**, select the computers, AD groups, and users this policy should apply to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;9. Click **Create** to activate the policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Example from the documentation:**&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To block processes like `cmd.exe`, `powershell.exe`, and `taskmgr.exe` (often used for admin tasks), you can define each as an executable in your Block policy scope [Create a new advanced policy to block Winlogon](&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon" href="https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon" target="_blank"&gt;https://docs.cyberark.com/epm/latest/en/content/security/secureendpoints.htm#Step2CreateanewadvancedpolicytoblockWinlogon&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 2. Block Access to Windows Services&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Block the Services Management Console**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Create a Block policy for `services.exe`:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- **Filename**: is exactly `services.exe`&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- **Original filename**: is exactly `SERVICES.EXE`&lt;/P&gt;&lt;P&gt;&amp;nbsp;- This will prevent users from launching the Services management console [Community answer](&lt;A alt="https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4" href="https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4" target="_blank"&gt;https://community.cyberark.com/s/question/0D5Ht0000A9FVWVKQ4&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- **Restrict Service Access via User Policy**:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Go to **Policies** &amp;gt; **User policies** &amp;gt; **Create user policy**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Set **Type** to **Services access**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Details &amp;gt; User permissions**, select **No access**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Scope**, add the specific service (e.g., `Spooler` for the Print Spooler).&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Under **Targets**, select the relevant users/computers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Click **Create** [Prevent users from modifying the print spooler service](&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice" href="https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice" target="_blank"&gt;https://docs.cyberark.com/epm/latest/en/content/featurespotlight/windowsprintspoolerelevation.htm#Preventusersfrommodifyingtheprintspoolerservice&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;### 3. General Guidance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- You must define each process or service you want to block individually, as EPM does not support blocking all administrative tasks as a group.&lt;/P&gt;&lt;P&gt;- Common admin tools to consider blocking: `cmd.exe`, `powershell.exe`, `taskmgr.exe`, `regedit.exe`, `mmc.exe`, `services.exe`, and others as needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**Note:** Always test your policies in a controlled environment before deploying broadly to avoid accidentally blocking legitimate business processes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you need to block additional tools or scripts, repeat the process for each relevant executable or service.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 18:30:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419122#M9060</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-13T18:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419123#M9061</link>
      <description>&lt;P&gt;I have my Sets which have been built based on users usage. On ech sets I know more or less what users need to access or not for their daily tasks.&lt;/P&gt;&lt;P&gt;For example, for Set 1  users must access to network properties but Set 2 they should not have access.&lt;/P&gt;&lt;P&gt;You mean that by default Set 2 users are blocked by the OS to access network properties (or some parameters)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 06:55:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419123#M9061</guid>
      <dc:creator>Faab</dc:creator>
      <dc:date>2025-05-14T06:55:03Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419124#M9062</link>
      <description>&lt;P&gt;When you create a new policy create an administrative task as shown here you can select then Networking as that's what you need right so users can select networking properties. I presume this will then let your users access network properties - by creating a new Definition within the SET. &lt;span class="lia-inline-image-display-wrapper" image-alt="068Vy00000WwKZ0IAN.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/92347iC6027285B7F68B94/image-size/large?v=v2&amp;amp;px=999" role="button" title="068Vy00000WwKZ0IAN.jpg" alt="068Vy00000WwKZ0IAN.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/92349iCA0819E7AACCC782/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png" alt="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 07:04:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419124#M9062</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T07:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419125#M9063</link>
      <description>&lt;P&gt;When you create a new policy create an administrative task as shown here you can select then Networking as that's what you need right so users can select networking properties. I presume this will then let your users access network properties - by creating a new Definition within the SET. &lt;span class="lia-inline-image-display-wrapper" image-alt="068Vy00000WwKZ0IAN.jpg"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/92347iC6027285B7F68B94/image-size/large?v=v2&amp;amp;px=999" role="button" title="068Vy00000WwKZ0IAN.jpg" alt="068Vy00000WwKZ0IAN.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/92349iCA0819E7AACCC782/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png" alt="Field_Content_versions_oct20__068Vy00000WwOVlIAN.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 07:04:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419125#M9063</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T07:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419126#M9064</link>
      <description>&lt;P&gt;Yes but by this way i can only allow elevate action on network properties. If I want to BLOCK network properties access to users, how to do it?&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 09:29:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419126#M9064</guid>
      <dc:creator>Faab</dc:creator>
      <dc:date>2025-05-14T09:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419127#M9065</link>
      <description>&lt;P&gt;I just elevated network properties we seem to have it as an Allow policy possible via the above apologies it's been a while since it was setup - not sure on blocking you will have to test it by doing a manual block process? but also ensure this DLL doesn't block anything else by checking the audits I guess if it works - I'd target the policy to your device and some UAT's - &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To block the elevation of a specific DLL such as `netshell.dll` using CyberArk Endpoint Privilege Manager (EPM), you would create an advanced Windows policy with the "Block" action and define the DLL as the application definition. Here’s how you can do it based on the available documentation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. In the EPM management console, click **Policies**.&lt;/P&gt;&lt;P&gt;2. In the Policies dropdown list, ensure **Application policies** is selected, then click **Create advanced policy**.&lt;/P&gt;&lt;P&gt;3. In the Create advanced application policy window:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Name your policy (e.g., "Block netshell.dll Elevation").&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Windows** as the platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Block** as the action.&lt;/P&gt;&lt;P&gt;4. Click **Continue**.&lt;/P&gt;&lt;P&gt;5. Under **Scope**, click **Add definition**.&lt;/P&gt;&lt;P&gt;6. In the Application definition window:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Set the definition type to **DLL**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Specify the filename as `netshell.dll`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- (Optionally) Add additional parameters such as path or publisher if you want to be more specific.&lt;/P&gt;&lt;P&gt;7. Under **Targets**, define the computers, users, and groups this policy should apply to.&lt;/P&gt;&lt;P&gt;8. Complete the policy creation process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This approach leverages the ability to block DLLs as part of application definitions in EPM Windows policies [Manage application definitions for Windows policies](https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Supportedapplicationdefinitions).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt; **Note:** The knowledge sources confirm that DLLs are a supported application definition type for block policies, but do not provide a step-by-step example specifically for `netshell.dll`. The steps above are based on the documented process for blocking DLLs in general. If you need to target a specific path or context, you can refine the definition further within the policy creation wizard.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 11:01:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419127#M9065</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T11:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419128#M9066</link>
      <description>&lt;P&gt;I just elevated network properties we seem to have it as an Allow policy possible via the above apologies it's been a while since it was setup - not sure on blocking you will have to test it by doing a manual block process? but also ensure this DLL doesn't block anything else by checking the audits I guess if it works - I'd target the policy to your device and some UAT's - &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To block the elevation of a specific DLL such as `netshell.dll` using CyberArk Endpoint Privilege Manager (EPM), you would create an advanced Windows policy with the "Block" action and define the DLL as the application definition. Here’s how you can do it based on the available documentation:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. In the EPM management console, click **Policies**.&lt;/P&gt;&lt;P&gt;2. In the Policies dropdown list, ensure **Application policies** is selected, then click **Create advanced policy**.&lt;/P&gt;&lt;P&gt;3. In the Create advanced application policy window:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Name your policy (e.g., "Block netshell.dll Elevation").&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Windows** as the platform.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Select **Block** as the action.&lt;/P&gt;&lt;P&gt;4. Click **Continue**.&lt;/P&gt;&lt;P&gt;5. Under **Scope**, click **Add definition**.&lt;/P&gt;&lt;P&gt;6. In the Application definition window:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Set the definition type to **DLL**.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- Specify the filename as `netshell.dll`.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;- (Optionally) Add additional parameters such as path or publisher if you want to be more specific.&lt;/P&gt;&lt;P&gt;7. Under **Targets**, define the computers, users, and groups this policy should apply to.&lt;/P&gt;&lt;P&gt;8. Complete the policy creation process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This approach leverages the ability to block DLLs as part of application definitions in EPM Windows policies [Manage application definitions for Windows policies](https://docs.cyberark.com/epm/latest/en/content/policies/windowspolicies-newui.htm#Supportedapplicationdefinitions).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt; **Note:** The knowledge sources confirm that DLLs are a supported application definition type for block policies, but do not provide a step-by-step example specifically for `netshell.dll`. The steps above are based on the documented process for blocking DLLs in general. If you need to target a specific path or context, you can refine the definition further within the policy creation wizard.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 11:01:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419128#M9066</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T11:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419129#M9067</link>
      <description>&lt;P&gt;yeah he's right if you ain't ticked it maybe you dont need to create a block policy as the answer is theory only - I wonder you can create a GUI block prompt instead saying you cannot elevate this, we do this for many things like manual installs of VS, Chrome it reduces the noise. &lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 12:30:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419129#M9067</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T12:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419130#M9068</link>
      <description>&lt;P&gt;yeah he's right if you ain't ticked it maybe you dont need to create a block policy as the answer is theory only - I wonder you can create a GUI block prompt instead saying you cannot elevate this, we do this for many things like manual installs of VS, Chrome it reduces the noise. &lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 12:30:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419130#M9068</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-14T12:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419131#M9069</link>
      <description>&lt;P&gt;Hello @Fabio MORBIDUCCI​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you received an answer to your question? If so, we kindly encourage you to share it with us.&lt;/P&gt;&lt;P&gt;Your insights could be valuable to other community members in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Isar.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 07:21:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419131#M9069</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-22T07:21:55Z</dc:date>
    </item>
    <item>
      <title>Re: Administration tasks block</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419132#M9070</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;You can block some administrator tasks. I have attached a screenshot of the policy. You can configure it for users and groups, and device management as well. &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Vy00000Z20CqIAJ.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/92511i172275D2003A5AE6/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Vy00000Z20CqIAJ.png" alt="Field_Content_versions_oct20__068Vy00000Z20CqIAJ.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 13:18:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/administration-tasks-block/m-p/1419132#M9070</guid>
      <dc:creator>Rmahalle</dc:creator>
      <dc:date>2025-05-29T13:18:40Z</dc:date>
    </item>
  </channel>
</rss>

