We take the security of our systems seriously, and we value the security community. The responsible disclosure of security vulnerabilities helps us ensure the security and privacy of Clipperz users.
We require that all researchers:
- make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- perform research only within the scope set out below;
- use the identified communication channels to report vulnerability information to us;
- keep information about any vulnerabilities you’ve discovered confidential between yourself and Clipperz until we’ve had 30 days to resolve the issue.
If you follow these guidelines when reporting an issue to us, we commit to:
- not pursue or support any legal action related to your research;
- work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);
- publicly recognize your contribution (website, twitter, …), if you are the first to report the issue and we make a code or configuration change based on the issue.
You may want to make the best of the information available from these sections of our website:
- web app: online vault and password manager
- company website
Out of scope
In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:
- findings from physical testing such as office access (e.g. open doors, tailgating);
- findings derived primarily from social engineering (e.g. phishing, vishing);
- findings from applications or systems not listed in the ‘Scope’ section;
- UI and UX bugs and spelling mistakes;
- network level Denial of Service (DoS/DDoS) vulnerabilities.
Things we do not want to receive:
- Personally identifiable information (PII)
How to report a security vulnerability?
If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing Giulio at firstname.lastname@example.org. Please include the following details with your report:
- description of the location and potential impact of the vulnerability;
- detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us);
- your name/handle and a link for recognition.
If you’d like to encrypt the information, please use Giulio’s PGP key.
Based on the Open Source Responsible Disclosure Framework by Bugcrowd, licensed under a Creative Commons Attribution 4.0 International License.