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 incidentmanager@eyeon.nl;
- 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:
- After receiving your e-mail, you will receive an acknowledgment of receipt. We will do everything in our power to contact you within 3 working days with a first response.
- Contact details shared with us, will only be used to communicate about this incident report. We will not share your contact details with other parties unless we are legally obligated to do so or if we suspect you of not following our instructions. In this case, we will report this to the appropriate authorities.
- We will handle your report with strict confidentiality, and not pass on your details to third parties without permission.
What we will strive to:
- We will keep you informed of the progress toward 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.
Version date: February 2024