- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
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
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
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
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:
=========
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
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: /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
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:
=========
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
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
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:
=========
The sample epmp files can be found attached in this Knowledge Article.