Vulnerability Disclosure Program
Last Updated: May 21, 2020
The information on this page is intended for security researchers interested in responsibly reporting security vulnerabilities to the Zscaler security team.
Security requires transformation and there is no better way to transform a security program than to engage directly with our customers and users. It is that engagement, along with a strong belief in the collaboration with the security community, that is the key to maintaining a secure environment for all of our users. If you believe you've discovered a security vulnerability on or within a Zscaler product, service, or application, we strongly encourage you to inform us as quickly as possible. We ask that such vulnerability reports be kept private and researchers not make those public until we have resolved the issue.
In return, we will work to review reports and respond in a timely manner. Our bug bounty partner, Bugcrowd, will engage with you initially to triage your submission. Zscaler will not seek judicial or law enforcement remedies against you for identifying security issues, so long as you (1) comply with the policies set forth herein; (2) comply with Bugcrowd’s Standard Disclosure Terms; (3) do not compromise the safety or privacy of our users; and (4) do not destroy any sensitive data you might have gathered from Zscaler as part of your research once issues are resolved; and (5) agree to and comply with Zscaler's Confidentiality terms below.
By engaging or participating in and/or submitting a security vulnerability to Zscaler, you agree to comply with the following confidentiality provisions.
“Confidential Information” means (i) all Zscaler information obtained during security testing or via your participation in the Zscaler Vulnerability Disclosure Program, (ii) all information disclosed to you in connection with the Bugcrowd Bounty Brief, and (ii) all submissions by you. You are not granted any rights in Zscaler’s Confidential Information or intellectual property by engaging in any testing or participating in Zscaler’s Vulnerability Disclosure Program.
Confidential Information does not include information that (i) is or becomes publicly available through no fault of your own and without breaching these provisions, (ii) is independently developed without use of or reference to Confidential Information, or (iii) is or becomes known by you from a source not bound by confidentiality restrictions.
Before engaging in any testing or submitting findings you agree (i) to hold Confidential Information in strict confidence, (ii) to protect such Confidential Information from unauthorized use or disclosure, (iii) to not disclose such Confidential Information to any third party including the public, (iv) to not use such Confidential Information for any purpose outside the scope of participating in Zscaler’s Vulnerability Disclosure Program, and (v) to notify Zscaler immediately upon discovery of any loss or unauthorized disclosure of Confidential Information. Notwithstanding the foregoing, you may disclose Zscaler’s Confidential Information to Zscaler or to Bugcrowd via the Bugcrowd partner portal.
Thanks for your help!
Vulnerability Program Scope & Rules
We are primarily interested in hearing about the following vulnerability categories:
Sensitive Data Exposure – Cross Site Scripting (XSS) Stored, SQL Injection (SQLi), etc.
Authentication or Session Management related issues.
Remote Code Execution.
Particularly clever vulnerabilities or unique issues that do not fall into explicit categories - show us your fancy footwork!
Out of Scope
The following vulnerability categories are considered out of scope of our responsible disclosure program and should be avoided by researchers.
Denial of Service (DoS) – Either through network traffic, resources exhaustion or others
Issues only present in old browsers/old plugins/end-of-life software browsers
Phishing or social engineering of Zscaler employees, users or clients
Systems or issues that relate to Third-Party technology used by Zscaler
Disclosure of known public files and other information disclosures that are not a material risk (e.g.: robots.txt)
Any attack or vulnerability that hinges on a user’s computer first being compromised
Please note that you are expected to engage in security research responsibly. For example, if you discover a publicly exposed password or key, you should not use the key to test the extent of access it grants or to download or exfiltrate data in order to prove it is an active key. Similarly, if you discover a successful SQL injection, you are expected not to exploit the vulnerability beyond any initial steps needed to demonstrate your proof-of-concept.
Excessive exfiltration or downloading of Zscaler data, or demanding payment in return for destruction of Zscaler data, will be considered outside of the scope of this program, and Zscaler will reserve all of its rights, remedies, and actions to protect itself and its users.
Our public program currently does not provide any monetary reward beyond Zscaler’s eternal gratitude. If you are a Bugcrowd researcher, you can also claim your submission below for kudos. If you are interested in helping us in a more dedicated manner as a security researcher in our Private Program, please contact [email protected] with your request and justification.
At Zscaler’s sole discretion, we may make exceptions to this policy for exceptional contributions.
Reporting a Security Vulnerability
Please use the form below to report security vulnerabilities to Zscaler through our Bugcrowd partner portal. Zscaler generally scores vulnerability based on the CVSS Score.