Vulnerability Disclosure Policy

1. Introduction

This vulnerability disclosure policy (policy) applies to any vulnerabilities you are considering reporting to us, FinBoGo Limited (CRN: 15397665) (FinBoGo, we, us, our). Please read this policy in full, before you report a vulnerability and follow its guidance.

We value those who take the time and effort to report security vulnerabilities in accordance with this policy, however, please note that we do not offer monetary rewards for vulnerability disclosures.

2. Reporting

If you believe you have found a security vulnerability, please submit your report to us using vulnerability@finbogo.com.

In your report, please include details of:

• the website, IP or page where the vulnerability can be observed;
• a brief description of the type of vulnerability (i.e. “XSS vulnerability”); and
• the steps to reproduce the vulnerability. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately and also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

3. 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 will also aim to keep you informed of our progress.

We assess the priority for remediation by looking at the impact, severity and exploit complexity of the vulnerability. Please note that vulnerability reports might take some time to triage or address. You are welcome to enquire on the status of your report but please avoid sending multiple enquiries and limit these to no more than one enquiry every 14 days to allow our team the time to focus on the remediation.

We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

Once your vulnerability has been resolved, we welcome requests to disclose your report. We'd like to unify guidance to affected users, and therefore ask that you continue to coordinate public release with us.

4. Guidance

You MUST NOT:

• break any applicable laws or regulations;
• access unnecessary, excessive or significant amounts of data;
• modify data in FinBoGo's systems or services;
• use high-intensity invasive or destructive scanning tools to find vulnerabilities;
• attempt or report any form of denial of service (i.e. overwhelming a service with a high volume of requests);
• disrupt FinBoGo's services or systems;
• submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with “best practice” (i.e. missing security headers);
• submit reports detailing TLS configuration weaknesses (i.e. “weak” cipher suite support or the presence of TLS1.0 support);
• communicate any vulnerabilities or associated details other than by means described in the published security.txt;
• social engineer, 'phish' or physically attack FinBoGo's staff or infrastructure; or
• demand financial compensation in order to disclose any vulnerabilities.

You MUST:

• always comply with data protection rules and must not violate the privacy of FinBoGo's users, staff, contractors, services or systems. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services; and
• securely delete all data retrieved during your research as soon as it is no longer required or within 14 days of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

5. 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 FinBoGo or any of its partner organisations to be in breach of any legal obligations.