Coordinated Vulnerability Disclosure Statement
At Port of Amsterdam the security of our systems is top priority. No matter how much effort we put into system security, there might be vulnerabilities present. If you discover a vulnerability, we would like to know about it so we can take steps to address it. We would like to ask you to help us protect our clients and our systems.
Do's
- Report the vulnerability as quickly as is reasonably possible, to minimise the risk of hostile actors finding it and taking advantage of it.
- 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.
Don'ts
- Reveal the vulnerability or problem to others until it is resolved.
- Build your own backdoor in an information system with the intention of then using it to demonstrate the vulnerability because doing so can cause additional damage and create unnecessary security risks.
- Utilise a vulnerability further than necessary to establish its existence.
- Copy, modify or delete data on the system. An alternative for doing so is making a directory listing of the system.
- Make changes to the system.
- Repeatedly gain access to the system or sharing access with others.
- Use brute force attacks, attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties to gain access to the system.
Out of scope
The following issues are generally considered out of scope unless there is a clear and demonstrable security impact:
- User enumeration that does not enable account takeover, credential stuffing, password reset abuse, or personal data disclosure.
- Clickjacking on pages without authenticated functionality or sensitive user actions.
- Volumetric denial-of-service (DoS) attacks or traffic flooding.
- CSRF on non-authenticated or non-state-changing endpoints.
- Self-XSS requires user interaction such as console execution or browser configuration changes.
- XSS affecting only unsupported or end-of-life browsers.
- Content spoofing or text injection without XSS, phishing risk, or data exposure.
- Missing rate limiting unless it demonstrably enables account takeover or abuse.
- Automated scanner output without proof-of-concept and impact analysis.
- Missing cookie flags on cookies that do not contain session identifiers or sensitive data.
- Missing security headers without demonstrated exploitability.
- Version disclosure without a known exploitable vulnerability.
- Directory listing of non-sensitive public content.
- SSL/TLS best-practice issues without practical exploitability.
- Vulnerabilities in third-party services are outside our control.
- Social engineering or phishing attacks.
- Physical access attacks.
- Theoretical issues without reproducible proof-of-concept.
Submit your findings
Whether it's a unsecured page or other vulnerability; report it via mail:
infosec@portofamsterdam.com
What we promise
- We will respond to your report within 5 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 concerning the report.
- We will not pass on your personal details to third parties without your permission, unless it is necessary to comply with a legal obligation. Reporting under a pseudonym or anonymous is possible.
- We will keep you informed of the progress towards resolving the problem.
- In the public information concerning the reported problem, 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.
This Responsible Disclosure policy is based on an example written by Floor Terra and the Responsible Disclosure Guideline of the NCSC.