Responsible Disclosure

At our hospital Ziekenhuis Amstelland, 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 security@zha.nl
  • 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;
  • Keep the engagement with our health care professionals to a bare minimum, your primary point of contact is our Security department;
  • Contact us in advance if you need to perform an excessive number of tests or requests to prove your finding as we might be able to provide a test system;

We expect you not to

  • Install malware;
  • Copy, change or delete data in a system (an alternative to this is making a directory listing of a system);
  • Make changes to any system;
  • Repeatedly access the system or share access with others than designated persons at Ziekenhuis Amstelland;
  • Use so-called “brute force” to access systems, use (distributed) denial-of-service or social engineering;
  • 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, spam or applications of third parties;
  • Perform any action that might potentially have a disruptive effect on our systems;

What we promise

  • We will respond to your report within 2 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 a publication concerning the problem reported, we will give not your name as the discoverer of the problem (unless you desire otherwise);
  • 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. Given the nature and social role of the hospital in our community, our reward is a T-shirt with the text “I hacked the hospital and all I got was this lousy t-shirt" and (if you desire) a named reference in our Hall of Fame;

Out of scope vulnerabilities

When reporting vulnerabilities, please consider the attack scenario and security impact for our business. Anything default found by any average vulnerability scanning tool will be considered out of scope, unless combined with a realistic attack vector or CVE publication. This includes the following vulnerabilities:

  • Missing HTTP security Headers that do not directly lead to a vulnerability, such as:
    • Content-Security-Policy, Strict Transport Security, X-Content-Type-Options, X-XSS-Protection, X-Download-Options, X-XSS-Protection
    • X-Frame-Options (unless there is a well-defined risk), Host header Injection with no demonstrable impact
    • Feature/Permissions Policy
    • Missing cookie flags on cookies that do not hold session or other sensitive information
    • Information Disclosure – default exposed config files with no sensitive data
    • Open redirect vulnerabilities without additional security impact
    • Content spoofing and text injection issues without showing an attack vector or being able to modify HTML/CSS
    • Denial of Service and Social Engineering attacks

  • Missing HTTP security Headers that do not directly lead to a vulnerability, such as:
    • Vulnerability reports from automated tools or without validation
    • Observations related to a missing DMARC policy for any domain related to the hospital
    • Observations related to a missing CAA record for any domain related to the hospital

  •  Respected reporters of incidents
    • Chetan lakhara
      Himanshu
      Mushkan Shaikh

We strive to resolve all problems as quickly as possible, and we would like to play an active role in any publication of the problem after it is resolved.