Vulnerability Reporting

If you have found a vulnerability with any CYE website, please report it here, please include as much details as possible.

We may contact you regarding this issue should we require further information to effectively diagnose and fix it.

Thank you for your help in keeping CYE safe

Vulnerability Policy

Introduction

This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to a CYE Sailing Centre related website.

We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.

Reporting

If you believe you have found a security vulnerability please report it above by filling out the form with details of:

• The URL where the issue has been found.
• A brief description of the type of vulnerability, for example; “XSS vulnerability”.
• Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

What to expect

After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days. We’ll also aim to keep you informed of our progress.

Guidance

You must NOT:

• Break any applicable law or regulations.
• Access unnecessary, excessive or significant amounts of data.
• Modify data on our systems or services.
• Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
• Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
• Disrupt our services or systems.
• Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice”, for example missing security headers.
• Communicate any vulnerabilities or associated details other than by means described in the published security.txt.
• Social engineer, ‘phish’ or physically attack the Organisation’s staff or infrastructure.
• Demand financial compensation in order to disclose any vulnerabilities.

You must:

• Always comply with data protection rules and must not violate the privacy of any data the we hold. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
• Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause us to be in breach of any legal obligations.