Skip to main content

Deploying the Nudge Security Browser Extension Using GPO

Velizar Demirev avatar
Written by Velizar Demirev
Updated over a week ago

This article walks through how to deploy the Nudge Security Chrome browser extension to Windows devices using Group Policy Objects (GPO) and a registry-based policy configuration. This approach ensures the extension is properly configured with your organization’s deployment key and reports back to Nudge Security.

In this article we will use Google Chrome as an example but similar steps apply for other browsers.

Prerequisites

Before you begin, make sure you have:

  • Administrative access to Group Policy Management

  • Google Chrome installed on target machines

  • The Deployment Key from the PowerShell file generated from the Nudge Security app

    • You can find this in Step 2 of the browser extension deployment instructions

    • You’ll need the value labeled nudge-security-deployment-key

Step-by-Step Deployment via GPO

1. Open the Group Policy Editor

  1. Open Group Policy Management.

  2. Create a new GPO or edit an existing one that applies to the target computers.

  3. Navigate to:

Computer Configuration
└─ Preferences
└─ Windows Settings
└─ Registry

2. Create the Registry Policy Key

  1. Right-click in the right-hand pane and select New > Registry Item.

  2. Leave all default options as-is.

  3. Paste the following into the Key Path field, then click OK:

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\diaecjfdpohehjhliaephjnpnlmeajfa\policy

This key defines the policy location for the Nudge Security Chrome extension.

3. Create the Registry Value for the Deployment Key

  1. Right-click again in the right-hand pane and select New > Registry Item.

  2. Leave all default options in place.

  3. Use the same Key Path as above:

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\3rdparty\extensions\diaecjfdpohehjhliaephjnpnlmeajfa\policy

In the Value name field, enter:

deployment_key

Change Value type to:

REG_SZ

Set Value data to the deployment key value found in the PowerShell file generated in Nudge Security (the nudge-security-deployment-key value).

Finally, Click OK to save.

4. Force a Policy Update

To apply the policy more quickly:

  • Run the following command on target devices:

gpupdate /force

Or wait for the next regular Group Policy refresh cycle.

Verifying the Deployment

On a device where the policy has applied:

  1. Open Google Chrome.

  2. Navigate to the following URL: chrome-extension://okpefoggmmkabdepnljgfmnbldmomaei/options.html

  3. Confirm that the extension loads successfully and shows a healthy status, indicating it has picked up the deployment key and is communicating with Nudge Security.

Additionally, if the extension does not appear or report correctly, double-check registry paths, value casing, and that the correct deployment key was used.

Summary

By deploying the Nudge Security browser extension via GPO and registry-based Chrome policies, you ensure:

  • Consistent installation and configuration across managed devices

  • Secure association with your Nudge tenant using the deployment key

  • Minimal end-user interaction required

Did this answer your question?