As we keep adding capabilities for our developer community, we wanted to share a summary of all the recent features we launched.
New functionalities to the CLI
In the past months we have added several new features to our Command Line Interface to help developers improve their workflows and improve how they manage secrets in their environments.
We have already mentioned several features in our previous blog post "Secure Secrets Management" like being able to inject secrets into environment variables, templatize files and transform secrets on the fly.
Now, we made it easier to manage non-interactive devices like servers thanks to service device keys that are simple tokens that allow access to your account and fetch the necessary secrets.
We have detailed how to generate new non-interactive devices keys in our CLI documentation: https://dashlane.github.io/dashlane-cli/personal/devices#register-a-new-non-interactive-device
We have also improved our login experience for SSO users: now all SSO users can use the CLI whether it's self-hosted or Confidential SSO. On top of that we have added extra security for the ones who share computers with their family: on MacOS we added a biometrics lock mechanism that ensures you're the only one able to access Dashlane CLI commands. Read our documentation about authenticating to the CLI here: https://dashlane.github.io/dashlane-cli/personal/authentication
For IT admins reading this post, we have heard your request, it is now possible to view and review Dark Web Insights of all your domains and employees right from the CLI. Dark Web Insights can identify vulnerabilities across all employees in an organization, even employees who don't have a Dashlane account yet. It does this by monitoring the dark web for employee email addresses to find domain-wide breaches and by scanning the web for any compromised organization information.
The full documentation is available here: https://dashlane.github.io/dashlane-cli/business/dwi
Github Action for loading secrets into GitHub's CI/CD
To streamline the experience for developers when they build, test and deploy code with their CI/CD we built a new GitHub action that allows to fetch secrets and inject them into following steps of the pipeline.
The action is available on GitHub's marketplace: https://github.com/marketplace/actions/load-secrets-from-dashlane
The GitHub action will be able to access a vault containing the needed secrets and inject them into pipeline environment variables, it could be password, secure notes or secrets and it supports transformation operations similarly to our CLI (documentation about transformations: https://dashlane.github.io/dashlane-cli/personal/secrets/read#transformer).
For instance here is a sample code that get secrets and passes them to the next job:
Here is the output once run:
As you can see it's easy and efficient to pass secrets to your CI/CD while staying in control of them via the usual Dashlane interface you use everyday.
Our GitHub action source code is available here: https://github.com/Dashlane/load-secrets-action
VS Code Extension
Visual Studio Code is one of the most used IDE and we wanted to provide developers with quick access to their vault and secrets while developing.
To start with we integrated quick actions to fetch passwords and secure notes right from the VS Code Command Palette.
Visual Studio Code is one of the most used IDE and we wanted to provide developers with quick access to their vault and secrets while developing.
To start with we integrated quick actions to fetch passwords and secure notes right from the VS Code Command Palette.
The extension is available on Microsoft's marketplace: https://marketplace.visualstudio.com/items?itemName=Dashlane.dashlane-vscode
Our VS Code extension source code is available here: https://github.com/Dashlane/dashlane-vscode
There is much more to come for the VS Code extension in the near future and your feedback is more than welcome!
Self-Hosted SIEM integration via FluentBit
Thanks to the Dashlane CLI it is possible to retrieve audit logs. We built a self-hosted mechanism to retrieve those logs and inject them into your own SIEM.
Dashlane Audit Logs Manager project (https://github.com/Dashlane/dashlane-audit-logs) allows you to retrieve Dashlane's audit logs and send them in the SIEM or storage solution of your choice, using FluentBit.
At the moment, we provide out of the box configurations for the following solutions:
- Azure log analytics workspace
- Azure blob storage
- Splunk
- Elasticsearch
This list is not restrictive, as others destinations can be used. You can find the list of supported platforms on FluentBit's website: https://docs.fluentbit.io/manual/pipeline/outputs
As a reminder we also have direct SIEM integration for Splunk powered by confidential computing, you can read more about it here: https://www.dashlane.com/blog/siem-integration-confidential-computing
Even more projects!
We're really happy to share those exciting projects with you and there are even more to discover on our Developers page (https://www.dashlane.com/developers) and GitHub space (https://github.com/Dashlane).
There are also nice community maintained projects to try like Raycast and Alfred extensions! If you're a developer and want to build with us, reach out on our GitHub discussions channel: https://github.com/Dashlane/dashlane-cli/discussions
Sign up to receive news and updates about Dashlane
