Security Exploit Bounty Program

In order to be eligible for a bounty, your submission must be accepted as valid by Asana. We use the following guidelines to determine the validity of requests and the reward compensation offered.

I. Requirements:

a) Responsible Disclosure

Security of user data and communication is of utmost importance to Asana. In pursuit of the best possible security for our service, we welcome responsible disclosure of any vulnerability you find in Asana. Principles of responsible disclosure include, but are not limited to:

• Accessing or exposing only customer data that is your own.
• Avoiding scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site).
• Keeping details of vulnerabilities secret until Asana has been notified and had a reasonable amount of time to fix the vulnerability.
• Keeping within the guidelines of our Terms Of Service.*

_{*If you participate in our bug bounty program, regardless of whether or not you file any bugs or any rewards is awarded to you by Asana, and subject to Section III Rewards, below, the first three bullets of section 5.2 of Asana’s Terms of Service (the “Asana AUP”) do not apply to you solely to the extent that you are participating in Asana’s bug bounty program, which means that you adhere to the principles of responsible disclosure set forth above. In the event that you take any of the actions outlined in the first three bullets of the Asana AUP and act in a way that violates any of the principles of responsible disclosure set forth above or otherwise shows malicious intent as determined by Asana, such actions will be deemed a breach of Asana’s Bug Bounty Program and Terms of Service, and Asana may pursue any remedies available to it under applicable law.}

b) Reproducibility

Our engineers must be able to reproduce the security flaw from your report. Reports that are too vague or unclear are not eligible for a reward. Reports that include clearly written explanations and working code are more likely to garner rewards.

II. Severity

In order to be eligible for a bounty, your submission must be accepted as valid by Asana. We use the following guidelines to determine the validity of requests and the reward compensation offered.

More severe bugs will be met with greater rewards. We are most interested in vulnerabilities with app.asana.com and asana.com. Other subdomains of asana are generally not eligible for rewards unless the reported vulnerability somehow affects app.asana.com or Asana customer data.

Examples of Qualifying Vulnerabilities

• Authentication flaws
• Circumvention of our Platform/Privacy permissions model
• Clickjacking
• Cross-site scripting (XSS)
• Cross-site request forgery (CSRF/XSRF)
• Mixed-content scripts on app.asana.com
• Server-side code execution

Examples of Non-Qualifying Vulnerabilities

• Denial of Service vulnerabilities (DOS)
• Possibilities to send malicious links to people you know
• Security bugs in third-party websites that integrate with Asana
• Mixed-content scripts on asana.com
• Insecure cookies on asana.com
• Social engineering attacks against Asana Support
• Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves be susceptible

III. Rewards

• Only 1 bounty will be awarded per vulnerability.
• If we receive multiple reports for the same vulnerability, only the person offering the first clear report will receive a reward.
• We maintain flexibility with our reward system, and have no minimum/maximum amount; rewards are based on severity, impact, and report quality.
• To receive a reward, you must reside in a country not on sanctions lists (e.g., Cuba, Iran, North Korea, Sudan & Syria). This is a discretionary program and Asana reserves the right to cancel the program; the decision whether or not to pay a reward is at our discretion.

IV. Contact

Please email us at security@asana.com with any vulnerability reports or questions about the program.