This is the Boundary Technologies Ltd vulnerability disclosure policy.
Boundary takes security issues extremely seriously and welcomes feedback from security researchers in order to improve the security of its products and services. We operate a policy of coordinated disclosure for dealing with reports of security vulnerabilities and issues.
This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to a Boundary Technologies Ltd (“Boundary”).
We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.
If you believe you have found a security vulnerability relating to Boundary’s system or products, please submit a vulnerability report to the address defined in the CONTACT field of the published security.txt file, or [email protected]
In your report please include details of:
- The hardware product, website, IP, page or mobile application 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.
After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 28 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.
Once your vulnerability has been resolved, we welcome requests to disclose your report. We’d like to unify our guidance, so please coordinate a public release with us.
Bug Bounty & Acknowledgement
We value those who expend time and effort on researching and disclosing vulnerabilities, however, as Boundary is an early-stage “startup” we are currently unable to offer a paid “Bug bounty” scheme. We will however show our appreciation by publishing resolved vulnerabilities, with attribution, in the “Hall of fame” area below with your permission.
You must NOT:
- Break any applicable law or regulations.
- Access unnecessary, excessive or significant amounts of data, for example, 2 or 3 records is enough to demonstrate most vulnerabilities, such as an enumeration or direct object reference vulnerability.
- Modify data in Boundary’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 Boundary’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 Boundary’s staff or infrastructure.
- Demand financial compensation in order to disclose any vulnerabilities.
- Always comply with data protection rules and must not violate the privacy of any data Boundary holds. 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).
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 Boundary or partner organisations to be in breach of any legal obligations.
Hall of Fame
This section lists people who have participated our program in and had security reports accepted by our security team.
Ritesh Gohil – LinkedIn Profile