At the Picqer, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.
If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.
Please do the following:
- E-mail your findings to email@example.com,
- Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data,
- Do not reveal the problem to others until it has been resolved,
- Do not use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties, and
- Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.
What we promise:
- We will respond to your report within 3 business days with our evaluation of the report and an expected resolution date,
- If you have followed the instructions above, we will not take any legal action against you in regard to the report,
- We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
- We will keep you informed of the progress towards resolving the problem,
- In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and
We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.
Not everything is a 'vulnerability'
Keep in mind that not everything you think is a security problem, is a real security risk for our application. Things like not using CSRF tokens in some places, or not using a certain HTTP header that some people may view as a 'best practice'. We try to make the best decisions in all cases, but we will reach sometimes a different conclusion then you.
Please respect our risk analysis and reasons for doing some things different then you may see as a best practise. As we are respecting all your findings and reports.
Thank you for your co-operation.
We want to say thanks to the following people, who helped us fix problems and disclosed security vulnerabilities responsibly:
- Prashant Vats
- Daksh Patel
- Shivam Kumar Agarwal
- Anas Laabab
- Kaushik Roy
- Ashish Padelkar
- Mansoor Gilal
- Ali Tabish
This document is based on the example at responsibledisclosure.nl