Dashlane Enterprise Password Manager is the first to implement secure enclaves and confidential computing.

Dashlane releases its new Confidential SSO feature to allow users to securely and seamlessly log into Dashlane with their existing company SSO credentials.

As cyber threats grow more advanced, Dashlane continually evolves to protect against them.

Dashlane is the first password manager to implement the power of secure enclaves and confidential computing to empower a simpler and more secure SSO integration, providing organizations with safe encryption.

This innovative technology is powered by Dashlane's patent-pending use of AWS Nitro Secure Enclaves to fully isolate the encryption keys, that enables organizations to be confident that cloud data is private and protected.

Unauthorized parties, including Dashlane, can’t see or access vault keys—they’re uniquely generated per user at the time of SSO setup.

With the spirit of transparency that Dashlane has always shown, the enclave’s code will be published, so that users and security experts can verify and validate the code and Dashlane's claims.

Dashlane Confidential SSO uses a product-agnostic architecture that supports all SAML 2.0-based Identity Providers (such as Azure AD, Google, Okta, and JumpCloud). IT admins find that Dashlane’s SSO fits seamlessly into their workflow, and since there’s no signup required for employees, it’s easier to drive adoption across the organization.

From now on, employees don't need to remember another password. Instead, they log in the same way as any other SSO app: With their secure SSO credentials.

How does Dashlane Confidential SSO work

When users log in with Dashlane Confidential SSO, they trust their IDP with their authentication credentials, which are transferred through a secure enclave. The enclave will only deliver secrets when presented with the correct credentials from the user. Secrets are transmitted through a secured tunnel, and the data processed inside the enclave remains confidential—even Dashlane cannot access it.

The Dashlane Blog