Vulnerability Disclosure Policy

Version 2020.06.04

Maintaining the security, privacy, and integrity of our products is a priority at MindTouch. Therefore, MindTouch appreciates the work of security researchers in order to improve our security posture. We are committed to creating a safe, transparent environment to report vulnerabilities.

If you believe you have found a security vulnerability that could impact MindTouch or our customers, we encourage you to report this right away. We will investigate all legitimate reports and fix the problem as soon as we can. We ask that you follow MindTouch’s Vulnerability Disclosure Policy and make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service during your research.


We require that all vulnerability reporters:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing
  • Perform research only within the scope set out below
  • Use the identified communication channels to report vulnerability information to us
  • Keep information about any vulnerabilities you’ve discovered confidential between yourself and MindTouch until we’ve had 90 days to resolve the issue

If you follow these guidelines when reporting an issue to us, we commit to:

  • Not pursue or support any legal action related to your research
  • Work with you to understand and resolve the issue quickly
    • Including an initial confirmation of your report within 72 hours of submission


Services that MindTouch provides, MindTouch customer sites, or any MindTouch product are in scope.

Out of scope

Any services hosted by 3rd party providers and services are excluded from scope. These services include:


In the interest of the safety of our users, staff, the Internet at large and you as a security researcher, the following test types are excluded from scope:

  • Findings from physical testing such as office access (e.g. open doors, tailgating)
  • Findings derived primarily from social engineering (e.g. phishing, vishing)
  • Findings from applications or systems not listed in the ‘Scope’ section
  • UI and UX bugs and spelling mistakes
  • Network level Denial of Service (DoS/DDoS) vulnerabilities

Things we do not want to receive:

  • Personally identifiable information (PII)
  • Credit card holder data

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of our products or platforms please send it to us by emailing [email protected] Please include the following details with your report:

  • Description of the location and potential impact of the vulnerability
  • A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us)

Effective date: June 4, 2020