Responsible Disclosure Policy

If you think you have found a security issue, please email us at security@tradeledger.io with a description and the step-by-step instructions on how to reproduce.

‍

Trade Ledger may reward for qualifying and non-duplicated reports depending on the severity, maximum impact, probability of attack-scenarios and the quality of the report.

‍

Please do not publicly disclose the issue until we have had a reasonable time to review it and address it. Do not interact with other accounts or teams without their explicit permission. Do not exploit any security issue for any other reason than for testing purposes.

‍

‍

‍

Purpose

To allow for the reporting and disclosure of vulnerabilities discovered by external entities.

‍

Scope

Trade Ledger’s Responsible Disclosure Policy covers applies to Trade Ledger’s core platform and its information security infrastructure, and to internal and external employees or third parties.

‍

Background

Trade Ledger is committed to ensuring the safety and security of our customers and employees. We aim to foster an environment of trust, and an open partnership with the security community, and we recognise the importance of vulnerability disclosures in continuing to ensure safety and security for all of our customers, employees, and company. We have developed this policy to both reflect our corporate values and to uphold our legal responsibility to good-faith security researchers that are providing us with their expertise.

‍

Legal Posture

Trade Ledger will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting inbox. We openly accept reports for the currently listed Trade Ledger products. We agree not to pursue legal action against individuals who:

• Engage in testing of systems/research without harming Trade Ledger or its customers.
• Engage in vulnerability testing within the scope of our vulnerability disclosure program.
• Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software.
• Adhere to the laws of their location and the location of Trade Ledger. For example, violating laws that would only result in a claim by Trade Ledger (and not a criminal claim) may be acceptable as Trade Ledger is authorising the activity (reverse engineering or circumventing protective measures) to improve its system.
• Refrain from disclosing vulnerability details to the public before a mutually agreed-upon timeframe expires.

How to Submit a Vulnerability Report

To submit a vulnerability report to Trade Ledger’s Product Security Team, please utilise the following email security@tradeledger.io.

‍

Preference, Prioritisation, and Acceptance Criteria

We will use the criteria from the next sections to prioritise and triage submissions.

‍

What we would like to see from you:

• Well-written reports in English will have a higher probability of resolution.
• Reports that include proof-of-concept code equip us to better triage.
• Reports that include only crash dumps or other automated tool output may receive lower priority.
• Reports that include products not on the scope list may receive lower priority.
• Please include how you found the bug, the impact, and any potential remediation.
• Please include any plans or intentions for public disclosure.

What you can expect from Trade Ledger:

• A timely response to your email.
• After triage, we will send an expected timeline, and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.
• An open dialog to discuss issues.
• Notification when the vulnerability analysis has completed each stage of our review.
• Credit after the vulnerability has been validated and fixed.

If we are unable to resolve communication issues or other problems, Trade Ledger may bring in a neutral third party to assist in determining how best to handle the vulnerability.