Dashlane Vulnerability Disclosure Policy
Introduction
Dashlane is committed to transparency and security. We believe that responsible disclosure of vulnerabilities contributes to the safety of our customers and the broader cybersecurity community. This policy outlines our approach to disclosing security vulnerabilities in Dashlane products and services in alignment with best practices recommended by the Cybersecurity and Infrastructure Security Agency (CISA).
Authorization
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Dashlane will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.
Guidelines
Under this policy, “research” means activities in which you:
- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
- Do not submit a high volume of low-quality reports.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
Test methods
The following test methods are not authorized:
- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing
Scope
The scope of this policy, as well as its exclusions, is maintainted current on our HackerOne bug bounty public page.
Any newly launched features or systems of Dashlane is included implicitly in the Scope of the Policy unless explicitly called out in the exclusions on HackerOne.
Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.
Reporting a vulnerability
Dashlane recognizes the importance of security researchers in helping keep our community safe. We encourage the responsible disclosure of security vulnerabilities directly to security@dashlane.com with the subject: "Security vulnerability report" or through our HackerOne bug bounty program.
Disclosure guidelines
What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:
- Before reporting a security issue, please read our security FAQs.
- Please provide thorough details regarding the vulnerability so that we can successfully recreate and address the issue. Describe the location the vulnerability was discovered and the potential impact of exploitation.
- Include proof of concept code, screenshots, or screencasts as needed.
- English is our working language.
- Please make a good faith effort not to leak, manipulate, or destroy any user data. Please only test against accounts you own yourself or with the explicit permission of the account holder.
- Please refrain from automated/scripted account creation.
- If your report includes sensitive information, please use the following GPG key:
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
- Within 3 business days, we will acknowledge that your report has been received.
- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
- We will maintain an open dialogue to discuss issues.
- Please be aware that depending on the severity of the vulnerability, we will need a reasonable amount of time to respond to and/or fix the reported issue.
HackerOne bug bounty program reward eligibility
Dashlane may provide rewards to eligible reporters of qualifying vulnerabilities through our HackerOne bug bounty program. Reward amounts may vary depending on the severity of the vulnerability reported.
Dashlane reserves the right to decide if the minimum severity threshold is met and whether the vulnerability was previously recorded.
To qualify for a reward under this program, you should:
- Be the first to report a specific vulnerability through our HackerOne bug bounty program.
- Send a clear textual description of the report along with steps to reproduce the vulnerability. Include attachments such as screenshots or proof of concept code as necessary.
- Disclose the vulnerability report directly and exclusively to us. Public disclosure or disclosure to third parties – including vulnerability brokers – before we address your report will result in forfeiting any potential reward.
Questions
Questions regarding this policy may be sent to security@dashlane.com . We also invite you to contact us with suggestions for improving this policy.
Dashlane appreciates and values the efforts of the security community in helping us maintain the highest level of security for our users.