At SecureMe2 we believe the safety of our systems is very important. Despite our concern for the security of our systems, it can happen that there is a weak spot. If you have found a weak spot in one of our systems, we would like to hear from you so that we can take measures as quickly as possible. We would like to work with you to better protect our customers and our systems.
Basic instructions and PGP-key can be found at https://www.secureme2.eu/.well-known/security.txt
We ask you:
- E-mail your findings to firstname.lastname@example.org. E-mail your findings to email@example.com. Add ‘vulnerability’ to the subject line to speed up the process.
- Not to misuse the problem by, for example, downloading more data than is necessary to demonstrate the leak or to view, delete or modify data from third parties,
- Do not share the problem with others until it has been resolved and erase all confidential data obtained through the leak immediately after the leak is closed,
- Not to use attacks on physical security, social engineering, distributed denial of service, spam or third-party applications, and
- Provide sufficient information to reproduce the problem so that we can resolve it as quickly as possible. Usually the IP address or URL of the affected system and a description of the vulnerability is sufficient, but more complex vulnerabilities may require more.
What we promise:
- We respond to your report within 3 days with our assessment of the report and an expected date for a solution,
- If you have complied with the above conditions, we will not take legal action against you regarding the report,
- We will treat your report confidentially and will not share your personal information with third parties without your permission unless it is necessary to fulfill a legal obligation. Reporting under a pseudonym is possible,
- We will keep you informed of the progress of solving the problem,
- In reporting on the reported problem we will, if you wish, state your name as the discoverer.
We strive to resolve all issues as quickly as possible and are happy to be involved in any publication about the issue after it has been resolved.
This disclosure is published under CCN 3.0 and available via https://responsibledisclosure.nl/