Channable

Responsible disclosure and bug bounty

At Channable the security of our systems is top priority. We appreciate responsible disclosure of security vulnerabilities. This document details our stance on reported security problems. No matter how much effort we put into system security, there might be vulnerabilities present. If you discover a vulnerability, we would like to know about it so we can take steps to address it. We would like to ask you to help us protect our clients and our systems.

Please do the following:

Do's:

  • Report the vulnerability as quickly as is reasonably possible, to minimise the risk of hostile actors finding it and taking advantage of it.
  • Report in a manner that safeguards the confidentiality of the report so that others do not gain access to the information.
  • Provide sufficient information to reproduce the problem, so we will be able to resolve it. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient. But complex vulnerabilities may require further explanation.
  • Use “SECURITY_RESEARCH” as referral code when creating a new Channable account for security research purposes.

Don'ts:

  • Reveal the vulnerability or problem to others until it is resolved.
  • Build your own backdoor in an information system with the intention of then using it to demonstrate the vulnerability, because doing so can cause additional damage and create unnecessary security risks.
  • Utilise a vulnerability further than necessary to establish its existence.
  • Copy, modify or delete data on the system. An alternative for doing so is making a directory listing of the system.
  • Make changes to the system.
  • Repeatedly gain access to the system or sharing access with others.
  • Use brute force attacks, attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties to gain access to the system.

What we promise:

  • We will respond to your report within 5 business days with our evaluation of the report and an expected resolution date.
  • If you have followed the instructions above, we will not take any legal action against you concerning the report.
  • We will keep you informed of the progress towards resolving the problem.

Bug Bounty:

Channable appreciates your help in keeping our systems safe. Depending on the vulnerability being reported, we may offer a reward for reporting it. Typical rewards are bounties up to 100 euros for low severity vulnerabilities, with higher bounty amounts for more severe issues. The specific reward for a given vulnerability is at our discretion. We will not award a bounty for vulnerabilities that:

  • Were found in a manner not conforming to our responsible disclosure guidelines.
  • Are already known to us.
  • Cannot be proven to be exploitable.
  • Are unconfirmed reports from automatic vulnerability scanners.
  • Are related to rate limits or brute force attacks.
  • Only demonstrate the ability to infer versions of software that we run (banner grabbing).
  • Are found in services that are out of scope.

The list of out-of-scope services includes:

  • channablestatus.com + *.channablestatus.com
  • channable.com + www.channable.com
  • academy.channable.com + internal-academy.channable.com
  • brand.channable.com+ brand.*.channable.com
  • docs.channable.com
  • helpcenter.channable.com
  • jobs.channable.com
  • status.channable.com
  • tech.channable.com
  • capig.channable.com
  • channablehelp.zendesk.com
  • channablenl.zendesk.com
  • documents.channable.com
  • gtm.channable.com
  • load.gtm.channable.com
  • reports.channable.com

This Responsible Disclosure policy is based on an example written by Floor Terra and the Responsible Disclosure Guideline of the NCSC.