EPM - How to block web browser extensions

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Endpoint Privilege Manager (EPM) Articles
4 min read
L0 Member
No ratings

Question: Is it possible to use the Idira EPM to create a policy that can block (blacklist) browser extensions and plugins running on web browser applications?

Answer: Yes, it is possible. Google Chrome and Mozilla FireFox have been tested to be working.
Using the similar steps below, you should be able to apply to different Browsers.

Disclaimer: The instructions below are for the new UI introduced in EPM version 22.6. For old UI, you can refer to this community link for the steps:
https://community.cyberark.com/s/question/0D52J000081I7gcSAC/can-cyberark-epm-be-able-to-block-web-browser-extensions-and-plugin-eg-google-chrome-firefox-and-ms-edgeie-browser-extensions-and-plugin

Steps

The steps below are for Google Chrome on Windows:
=========
1. In the EPM console, go to Policies and select "Create advanced policy".

2. Select "Continue" after you configured the below settings:
- Name: ***
- Platform: Windows
- Action: Allow

3. Under the Scope, add the following and press Done:
Publisher's signature starts with Google LLC
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4uJ.png

4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements.

5. In the options section, proceed to the Application access control and switched it ON.

6. Under the Files on the local disk sub-section, select Edit.
Proceed to Add Filename for 2 parameters below:
Location: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\Temp | Access control mode: Off
Location: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\ | Access control mode: Restrict
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4w5.png

7. Keep the rest as default (Or edit them if required) and proceed to create the policy.

8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon).
Remember to close all Google Chrome browsers and start them again in order for the Block extension to take effect.

9. As a test, when you attempt to add the browser extensions, the below error dialog should appear:
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4xD.png
=========

The steps below are for Google Chrome on macOS:
=========
1. In the EPM console, go to Policies and select "Create advanced policy".

2. Select "Continue" after you configured the below settings:
- Name: ***
- Platform: macOS
- Action: Allow

3. Under the Scope, add the following and press Done:
Publisher's signature starts with Google
eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P8ebP.jpg 

4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements.

5. In the options section, proceed to the Application access control and switched it ON.
eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P91T7.jpg 
6. Under the Files on the local disk sub-section, select Edit.
Proceed to Add Filename for 2 parameters below:
Location: /Users/*/Library/Application Support/Google/Chrome/Default/Extensions/Temp | Access control mode: Off
Location: /Users/*/Library/Application Support/Google/Chrome/Default/Extensions | Access control mode: Restrict
eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P8HBm.jpg 

eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P8LQg.jpg 

eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P8lcs.jpg 

7. Keep the rest as default (Or edit them if required) and proceed to create the policy.

8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon).
Remember to close all Google Chrome browsers and start them again in order for the Block extension to take effect.

9. As a test, when you attempt to add the browser extensions, the below error dialog should appear:
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EMVy00000P8WHH.png 
=========


The steps below are for Mozilla FireFox:
=========
1. In the EPM console, go to Policies and select "Create advanced policy".

2. Select "Continue" after you configured the below settings:
- Name: ***
- Platform: Windows
- Action: Allow

3. Under the Scope, add the following and press Done:
Publisher's signature starts with Mozilla Corporation
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4xN.png

4. For the Targets, Audit and End User UI sections, set them accordingly to your requirements.

5. In the options section, proceed to the Application access control and switched it ON.

6. Under the Files on the local disk sub-section, select Edit.
Proceed to Add Filename for the parameter below:
Location: %APPDATA%\Mozilla\Firefox\Profiles\*\extensions\ | Access control mode: Restrict
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4xw.png

7. Keep the rest as default (Or edit them if required) and proceed to create the policy.

8. You can either proceed to push active policies to agents (via EPM console) or request settings from the end-user computer (via the EPM icon).
Remember to close all Mozilla FireFox browsers and start them again in order for the Block extension to take effect.

9. As a test, when you attempt to add the browser extensions, the below error dialog should appear:
ka3Vy000008nTOTIA2__eid=ka3Vy000008nTOT&feoid=00N2J000009R3kv&refid=0EM2J000004E4ya.png
=========

The sample epmp files can be found attached in this Knowledge Article.

Rate this article:
  • 5320 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:50 AM
Updated by: