Credential Risk Detection is available to organizations on a Dashlane Business Plus plan.
Upgrade to Dashlane Business Plus

Estimated time to complete: 20 minutes

Admins can use the master data management (MDM) tool Group Policy (GPO) to set up Credential Risk Detection for company-managed Google Chrome and Microsoft Edge desktop browsers on Windows.

Note: You can't use Jamf on Windows or Intune and GPO on macOS.

More about Credential Risk Detection
What is GPO?
Looking to set up Risk detection on macOS using Jamf?
Looking to set up Risk detection on macOS using Intune?

Although Credential Risk Detection is most beneficial when rolled out to your entire organization, you can start with a smaller group (or just yourself) during setup and extend it to more employees anytime. To add more employees, update the groups included in your Credential Risk Detection policy.

Add employees to the policy

Process overview

Prerequisites

Make sure you have the appropriate access needed to set up Credential Risk Detection:

• Admin access to a Dashlane Business Plus account
• Admin access to Group Policy (GPO) on Windows
• Permission to deploy policies to devices using GPO

Set up Credential Risk Detection on Windows using GPO

Setting up Risk Detection involves four main steps:

1. Configure the Risk Detection policy
2. Confirm the policy was applied correctly
3. Deploy the Dashlane Extension
4. Turn on Risk Detection

If you prefer, watch the Windows + GPO step-by-step video

Review insights and take action

After Credential Risk Detection is turned on, any at-risk passwords entered by employees in company-managed desktop browsers will be logged in the Activity Log and displayed on the Insights tab on the Risk Detection page.

When you identify an employee with risky password practices, you can invite them to your Dashlane plan. With Dashlane, they can use the Password Generator to create strong, secure passwords and store their credentials safely in an encrypted vault.

More about Risk Detection insights

1: Configure the Risk Detection policy

Don't skip this step, even if you've already deployed the Dashlane extension.
What if the extension has already been deployed?

You must deploy the Credential Risk Detection policies before you deploy the Dashlane extension. This order ensures the extension installs silently. If you don't deploy the policies to your targeted machines, your employees will be asked to log in to Dashlane on every login screen. If you deploy the extension before the policies, employees might create a personal account before the policies are applied.

Note: If you're deploying to both Chrome and Edge, you must complete these steps for both browsers.

In the Dashlane Admin Console, start the setup:

1. Open the Dashlane Admin Console
2. From the menu, select Risk Detection. On the Risk Detection page, select Start setup.
   

   

3. Select the Group Policy (GPO) tab and the browsers you're deploying to. Ensure your selection is accurate before downloading the XML files so your GPO is created correctly.

   

4. In the Windows guidelines section, select Download all XML files.

   

5. On a domain-joined server, open Group Policy Management, right-click and select Run as administrator. You're going to create a new Policy Object

   

6. Right-click on Group Policy Object and select New

   

7. You can name this new GPO CRD Policy and select OK

   

8. Right-click on the CRD Policy you created and select Edit

   

9. Go to User Configuration, Preferences, Windows Settings, Registry

   

10. Drag the .xml templates you downloaded in the Admin Console and drop them in the Registry window

    

11. Select Yes when asked if you want to import the pasted document.

    

12. Close the Group Policy Management Editor

    

13. Back in the Group Policy Management window, right-click your OU (organizational unit) from the "Group Policy Management" folder and select Link an Existing GPO.

    

14. Select CRD Policy and OK

    

15. Right-click on CRD Policy in the Domains folders and select Enforced

    

After performing these steps, the deployment might take up to eight hours, but it's usually faster.

2: Confirm the policy was applied correctly

To ensure Risk Detection's proactive threat monitoring doesn't alert or disrupt employees, you must wait for the policy to take effect in your MDM before deploying the Dashlane extension to enrolled devices and activating the feature.

Check the policy was applied:

1. Using a device that was part of the group the script was deployed to, go to Registry Editor and select the following folders for Chrome and Edge:

   HKEY_LOCAL_MACHINE > Software > Policies > Google > Chrome > 3rdparty > extensions

   HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Edge > 3rdparty > extensions

   
2. You'll see a folder named using the Dashlane Extension ID. Under that folder, the policy folder contains the actual values of the Risk Detection policy.

   

In the Dashlane Admin Console, confirm the policy was applied:

1. On the Risk Detection page, go to step 2 and select the confirmation checkbox.
2. Select Continue.

   

3: Deploy the Dashlane Extension

You can skip this step if you've previously deployed the extension.

You must deploy the Credential Risk Detection policies before you deploy the Dashlane extension. This order ensures the extension installs silently. If you don't deploy the policies to your targeted machines, your employees will be asked to log in to Dashlane on every login screen. If you deploy the extension before the policies, employees might create a personal account before the policies are applied.

Return to step 1 to deploy the policy
What if the extension has already been deployed?

If you're deploying to both Chrome and Edge, repeat these steps for each browser.

Create new GPO policy

1. Open all folders within Group Policy Management until you see the "Group Policy Objects" folder. Right-click that folder and select New.

   

2. In the New GPO pop-up, enter "DashlaneGPO" or "Dashlane Extension" for the Name and then select OK.

   

3. Right-click your OU from the "Group Policy Management" folder and select Link an Existing GPO. For example, if the domain is "dashlanenyc.com" and the OU is "Dashlane-Client", the target computers are in the "Dashlane-Client" folder.

   

4. In the Select GPO pop-up, select the "Dashlane-GPO" you created and select OK.

   

In the Dashlane Admin Console:

• On the Risk Detection page, go back to step 3 and select Continue.

  

4: Turn on Risk Detection

Activate Risk Detection to get insights on risky password behavior across company devices. The associated activity logs detail the employee and the website accessed but don't include the password itself.

In the Dashlane Admin Console:

• On the Risk Detection page, go to step 4 and select Turn on.
  

  

After Credential Risk Detection is turned on, any at-risk passwords entered by employees in company-managed desktop browsers will be logged in the Activity Log and displayed on the Insights tab on the Risk Detection page.

When you identify an employee with risky password practices, you can invite them to your Dashlane plan. With Dashlane, they can use the Password Generator to create strong, secure passwords and store their credentials safely in an encrypted vault.

More about Risk Detection insights

Watch the Windows + GPO setup video

You can watch a step-by-step video of the Windows + GPO setup. Turn on the sound to hear the voiceover.

If you have any issues turning on this feature, please contact our Support team.

Contact an agent through the Admin Console
Chat with our bot

Common questions