Responsible Disclosure Policy

At Sketch the security of our systems, and our users, is a top priority. No matter how much effort we put into system security, there might still be vulnerabilities present. If you do discover a vulnerability, we want to know about it so we can take the correct steps to address it as quickly as possible. We’re asking for your help to protect our customers and our systems.

You can submit your findings by using our Responsible Disclosure Form at Zerocopter.

Scope

The following areas are considered in scope:

  • The sketch.cloud web application.
  • The sketch.cloud API.

The following areas are considered out of scope:

  • Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts)
  • Policies as opposed to implementations - email verification, password length or reuse, etc.
  • Spam (unless a specific vulnerability leads to easily sending spam)
  • Missing security headers or ‘best practices’ (except if you are able to demonstrate a vulnerability that makes use of their absence)
  • Vulnerabilties in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on sketch.cloud or related apps)
  • Distributed Denial of Service attacks (DDoS)
  • Social engineering attacks
  • Third party applications we make use of, but do not control. (e.g. a blog or newsletter hosted on an external service.)
  • Integrations and extensions created by third party developers using our public API.
  • Vulnerabilities related to our licensing system.
  • Vulnerabilities in the Sketch desktop app, unless that vulnerability has an effect on the sketch.cloud web app.

Dos

  • Do report the vulnerability as quickly as is reasonably possible, to minimise the risk of hostile actors finding it and taking advantage of it.
  • Do report your findings in a manner that safeguards the confidentiality of the report so that others do not gain access to the information.
  • Do 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. However, complex vulnerabilities may require further explanation.

Don’ts

  • Don’t reveal the vulnerability or problem to others until it is resolved.
  • Don’t 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.
  • Don’t utilise a vulnerability further than necessary to establish its existence.
  • Don’t copy, modify or delete data on the system. An alternative for doing so is making a directory listing of the system.
  • Don’t make changes to the system.
  • Don’t repeatedly gain access to the system or share access with others.
  • Don’t 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.

Our 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 not pass on your personal details to third parties without your permission, unless it is necessary to comply with a legal obligation. Reporting anonymously or under a pseudonym is possible.
  • We will keep you informed of the progress towards resolving the problem.
  • In the public information concerning the reported problem, we will give your name as the discoverer of the problem (unless you desire otherwise).

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication of the problem after it is resolved.

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