How to restrict/block browser extensions from installing on chrome and Edge for MacOS.

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

How to restrict/block browser extensions from installing on chrome and Edge for MacOS.

L1 Bithead

I've followed the same process outlined in the KB, however, it seems that the restriction is not applying for MacOS. I wanted to confirm if I may be missing anything in the policy configuration.

Field_Content_versions_oct20__068Vy00000b4e6rIAA.pngField_Content_versions_oct20__068Vy00000b5Ks8IAE.pngField_Content_versions_oct20__068Vy00000b4bILIAY.png

2 REPLIES 2

L5 Sessionator

We use jamf so can't really replicate - but silly question what if you gave yourself macos admin rights and added and extension via the browser/s and then checked the audit policy for the macos device specifically and see if you can create a block policy assuming by the logs, anyway if not try this ?

Add Comprehensive Folder Rules

Chrome:

/Users/*/Library/Application Support/Google/Chrome/Default/Extensions/

/Users/*/Library/Application Support/Google/Chrome/Profile*/Extensions/

Edge:

/Users/*/Library/Application Support/Microsoft Edge/Default/Extensions/

/Users/*/Library/Application Support/Microsoft Edge/Profile*/Extensions/

 

2. Ensure EPM Agent Has Full Disk Access

On the target macOS device:

  • Open System Settings > Privacy & Security > Full Disk Access
  • Grant access to:
    • CyberArk EPM Agent
    • Any associated system extensions

This can also be deployed via MDM (e.g., Jamf or Intune) using a configuration profile.

 

3. Confirm Advanced Policy Setup in CyberArk EPM

  • In the EPM Console, create a new policy using "Create Advanced Policy"
  • Set Platform = macOS
  • Add the folder access restriction rules listed above
  • Optionally, add executable rules:
  • Chrome: 
    • Publisher's signature starts with {"Google LLC"}
  • Edge: 
    • Publisher's signature starts with {"Microsoft Corporation"}

 

4. Perform Behavioral Testing and Log Review

  • Log in as a standard (non-admin) user
  • Attempt to install extensions in Chrome and Edge
  • Review the EPM logs:

/Library/Logs/CyberArk/epm.log

  • Look for entries with 
  • "Deny"
  •  
  •  related to the 
  • Extensions
  •  folder

5. Validate Policy Application

  • Ensure the policy is assigned to the correct macOS endpoint group
  • In Chrome, go to 
  • chrome://policy
  • In Edge, go to 
  • edge://policy
  • Confirm no enterprise-wide settings are overriding the folder restrictions

 

L4 Transporter

We use jamf so can't really replicate - but silly question what if you gave yourself macos admin rights and added and extension via the browser/s and then checked the audit policy for the macos device specifically and see if you can create a block policy assuming by the logs, anyway if not try this ?

Add Comprehensive Folder Rules

Chrome:

/Users/*/Library/Application Support/Google/Chrome/Default/Extensions/

/Users/*/Library/Application Support/Google/Chrome/Profile*/Extensions/

Edge:

/Users/*/Library/Application Support/Microsoft Edge/Default/Extensions/

/Users/*/Library/Application Support/Microsoft Edge/Profile*/Extensions/

 

2. Ensure EPM Agent Has Full Disk Access

On the target macOS device:

  • Open System Settings > Privacy & Security > Full Disk Access
  • Grant access to:
    • CyberArk EPM Agent
    • Any associated system extensions

This can also be deployed via MDM (e.g., Jamf or Intune) using a configuration profile.

 

3. Confirm Advanced Policy Setup in CyberArk EPM

  • In the EPM Console, create a new policy using "Create Advanced Policy"
  • Set Platform = macOS
  • Add the folder access restriction rules listed above
  • Optionally, add executable rules:
  • Chrome: 
    • Publisher's signature starts with {"Google LLC"}
  • Edge: 
    • Publisher's signature starts with {"Microsoft Corporation"}

 

4. Perform Behavioral Testing and Log Review

  • Log in as a standard (non-admin) user
  • Attempt to install extensions in Chrome and Edge
  • Review the EPM logs:

/Library/Logs/CyberArk/epm.log

  • Look for entries with 
  • "Deny"
  •  
  •  related to the 
  • Extensions
  •  folder

5. Validate Policy Application

  • Ensure the policy is assigned to the correct macOS endpoint group
  • In Chrome, go to 
  • chrome://policy
  • In Edge, go to 
  • edge://policy
  • Confirm no enterprise-wide settings are overriding the folder restrictions

 

  • 248 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!