Responsible Disclosure Policy

Last updated January 5, 2023

At Designware, the security of our systems and users is a top priority. No matter how much effort anyone puts into system security, there can still be vulnerabilities.

If you discover a vulnerability, we want to know about it so we can take the correct steps to address it as quickly as possible. We would like you to help us better protect our users and systems.

You can submit your findings (anonymously if desired) to [e-mail].

In-Scope:

• The designware.io web application.

• The designware.io API.

Out of Scope:

• Vulnerabilities that require access to an already compromised user account (unless access to an account exposes other accounts).

• Policies as opposed to implementations, such as email verification or password length or reuse.

• 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).

• Rate limits.

• Distributed Denial of Service attacks (DDoS).

• Social engineering attacks.

• Third party applications we make use of but do not control (i.e. a media library or social media service).

• Integrations and extensions created by third party developers using our public API.

Please:

• Do report the vulnerability as quickly as is reasonably possible to [e-mail], to minimize the risk of hostile actors finding or taking advantage of it.

• Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. 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.

• Don’t take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability, making changes to the system, or deleting or modifying other people’s data.

• Don’t build your own backdoor in a system, even if the intention is to demonstrate the vulnerability; doing so can cause additional damage and create unnecessary security risks.

• Don’t reveal the problem to others until it has been resolved.

• Don’t use attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties.

What We Promise:

• Your message will be read by a member of our team. If it is a legitimate or previously unknown security concern, we will respond to your report within 3 business days with our evaluation and an expected resolution date.

• If you have followed the instructions above, we will not take any legal action against you in regard to the report.

• We will handle your report with strict confidentiality and not share your personal details to third-parties without your permission.

• We will keep you informed of the progress towards resolving the problem.

• In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise).

• At present we have discontinued our bounty program, due to a high level of automated spam. We may consider issuing rewards on a case-by-case basis, in our sole discretion, depending on the nature and legitimacy of the security concern.

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.