Responsible Disclosure Policy

At Eye the security of our own systems is top priority. We put a lot of effort in trying to keep our systems secure. As a cybersecurity company, we know that 100% security does not exist. Therefore, there could be vulnerabilities in our system. We encourage you to contact us to report potential vulnerabilities in our systems. In this policy we would like to give security researchers guidelines for conducting vulnerability discovery activities as well as how to submit the discovered vulnerabilities to us.

This policy describes:

  • What systems and types of research are covered under this policy.
  • How to send us vulnerability reports.

  • How long we ask security researchers to wait before publicly disclosing vulnerabilities.


If you comply with our policy doing your security research, we will consider your research to be authorized. We will work with you to understand and resolve the issue quickly and will not recommended to pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.


This policy applies to all EYE system and services that are accessible via the internet.

Vulnerabilities found in systems from our vendors and clients fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us at

The following vulnerabilities are out of scope of this program :

  • Forms missing CSRF tokens (we require evidence of actual CSRF vulnerability)

  • Logout CSRF

  • Password and account recovery policies, such as reset link expiration or password complexity

  • Invalid or missing SPF (Sender Policy Framework) records

  • Content spoofing / text injection

  • Clickjacking and problems that are only exploitable via clickjacking

  • Issues without clearly identified security impact, missing security headers, or descriptive error messages

  • Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)

  • Self-exploitation (e.g., cookie reuse)

  • Missing security-related HTTP headers which do not lead directly to a vulnerability, including but not limited to X-Xss-Protection, X-Content-Type-Options, Content-Security-Policy-Report-Only, etc.

  • Self XSS vulnerabilities without evidence on how the vulnerability can be used to attack another user

  • Presence of autocomplete attribute on web forms

  • Missing secure cookie flags on non-sensitive cookies

  • Banner identification issues

  • Open ports which do not lead directly to a vulnerability

  • Open redirect vulnerabilities

  • Testing third party SaaS apps or services, except self-host, IaaS, or CDN assets

  • Defacing any assets, or doing anything that may result in brand damage

  • Attacks designed or likely to validate stolen credentials, credential reuse, account takeover (ATO), hijacking, or other credential-based techniques.

Please do the following

  • Notify us ( in Dutch or English as soon as possible after you discovered a real of potential security issue. We support PGP-encrypted emails for particularly sensitive information. You can find our public key on our website.

  • Report in a manner that safeguards the confidentiality of the report so that others do not gain access to the information.

  • Provide sufficient information to reproduce the problem, so we will be able to resolve it. 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, like proof of concept scripts or screenshots.


Under this policy, “research” means activities in which you:

  • Notify us as soon as possible after you discover a real or potential security issue.

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.

  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.

  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.

  • Do not submit a high volume of low-quality reports.

  • Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

The following test methods are not authorized:

  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data

  • Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing

What you can expect from us

We commit to coordinating with you as openly and as quickly as possible.

  • Within five business days, we will acknowledge that your report has been received.

  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.

  • We will maintain an open dialogue to discuss issues.

  • As a token of our gratitude for your assistance, we offer a reward for every report of a security problem that was not yet known to us. The reward will be determined based on the severity of the leak and the quality of the report.

  • Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely EYE Security, we may share your report with the Dutch National Cyber Security Centre or Digital Trust Center, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.


Questions regarding this policy may be sent to We also invite you to contact us with suggestions for improving this policy.