Read our guidelines for submitting a security vulnerability to Transportal. Page last updated August 2026

Introduction

At Transportal (accessible via www.thetransportal.com), we value the security of our systems and the trust of our users. We welcome feedback to help us keep our platform safe.

The vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to us (the “organisation”). We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always act 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.

This policy applies only to the following digital assets owned and operated by Transportal:

In Scope

  • `www.thetransportal.com`
  • The Transportal Common Data Environment (CDE) web applications (including DMS, Forms, Comms, and Assets modules accessible via our domain).
  • Out of Scope
  • Any third-party websites, integrations, or services hosted by external vendors.
  • Physical security of Transportal offices, properties, or data centres.
  • Social engineering, phishing, or baiting of Transportal employees or contractors.

Out of Scope

  • Any third-party websites, integrations, or services hosted by external vendors.
  • Physical security of Transportal offices, properties, or data centres.
  • Social engineering, phishing, or baiting of Transportal employees or contractors.

Reporting a security vulnerability

If you believe you have found a security vulnerability, please submit your report to us via our contact page on our website.

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, 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.

Submit a report

Guidance

You must not:

  • Break any applicable law or regulations.
  • Access unnecessary, excessive, or significant amounts of data.
  • Modify data in the Organisation’s 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 the Organisation’s 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.
  • Submit reports detailing TLS configuration weaknesses, for example “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 the Organisation’s staff or infrastructure.
  • Demand financial compensation in order to disclose any vulnerabilities.

You must:

Securely delete all data retrieved during your research as soon as it is no longer required or within one month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

Always comply with data protection rules and must not violate the privacy of the Organisation’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.

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

However, if legal action is initiated by a third party against you and you have complied with this policy, we can take steps to make it known that your actions were conducted in compliance with this policy.

What to expect when reporting

After you have submitted your report, we will aim to acknowledge receipt of your report within five working days and aim to triage your report within ten working days. We’ll also aim to keep you informed of our progress.

Priority for remediation is assessed by looking at the impact, severity, and exploit complexity. Vulnerability reports might take some time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days. This allows our teams 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.

Thank you for helping keep Transportal safe for everyone.

X