Responsible Disclosure Statement
At iWink, 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
- Submit your findings by using the following URL: https://app.zerocopter.com/rd/47b040f5-b67d-4ed8-9018-e9ce022afbcc.
- 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.
- 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 five business days with our evaluation of the report.
- If you have followed the instructions above, we will not take any legal action against you in regard to the report.
- We will 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).
- 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.
Of course, we take critical and medium-level security reports extremely serious. Some security issues, however, have a particularly low impact and will not be processed. For example; when the implementation of a mitigation disproportionately degrades the user-friendliness of our products. Or because a mitigation will be rolled out on a large scale in the near future.
Some examples of things not to report:
- Generic error messages (unless critical information is leaked)
- Availability of public files, such as robots.txt
- CSRF issues, where there is no direct consequence for end users. (For example for contact forms)
- SPF issues from domains that are not used for mail
- Missing DNSSEC records
- Missing CAA records
- Missing includeSubDomains or preloading in HSTS
- Missing CSP-headers
- Email spoofing where mail is marked as spam.