Vulnerability Disclosure Policy

Definition

Netskope takes the protection of our customers’ information and the products and services Netskope provides to them very seriously.

Netskope wants security researchers to feel comfortable reporting vulnerabilities they’ve discovered, as set out in this policy so that Netskope can remediate them and help us keep Netskope products and information safe.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long Netskope asks security researchers to wait before disclosing any vulnerabilities.

Compliance

If you comply with this policy during your security research and do not compromise the security of Netskope systems, Netskope’s customers’ data, or the safety or privacy of Netskope users, Netskope will work with you to understand and resolve the issue quickly and will not initiate or recommend legal action related to your research.

Netskope will be using your Name and Mail id (if required) while making public disclosures. Due to privacy concerns, If you do not wish to use the same, please notify Netskope in advance.

Guidelines

Netskope requires you to:

• Notify Netskope as soon as possible once you discover a real or potential security issue.
• Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and any access, copying, destruction or manipulation of data.
• Only use exploits to the extent necessary to confirm a vulnerability. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to “pivot” to other systems.
• Once you’ve established that a vulnerability exists, or encountered any of the sensitive data outlined below, you must stop your test and notify us immediately.
• Keep confidential any information about discovered vulnerabilities until announced by Netskope. For details, please review the Coordinated Disclosure section.
• Netskope encourages a coordinated public disclosure of security issues and expects security researchers to provide Netskope a reasonable time to fix the security issue before making any disclosure, public or otherwise.

Scope

This policy applies to all the products, services and infrastructure developed, managed and maintained by Netskope.

Additionally, vulnerabilities found in Netskope service providers’ systems fall outside of this policy’s scope and should be reported directly to the service provider according to their disclosure policy (if any). If you are not sure whether a system or endpoint is in scope or not, contact us at [email protected] before starting your research.

A subset of these systems may be eligible for bounties. Check Netskope’s program page on BugCrowd for the current list of bounty-eligible systems.

Rules of Engagement

The following test types are not authorized:

• User interface bugs or typos.
• Engage in Social Engineering.
• Introducing or adding a malware/malicious software.
• Network denial of service (DoS or DDoS) tests.
• Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing.

If you encounter any of the below on Netskope systems while testing within the scope of this policy, stop your test and notify us immediately:

• Personal Identifiable Information (PII)
• Customer Data or Account Credentials
• Financial information (e.g., credit card or bank account numbers)
• Proprietary information or trade secrets of companies of any party
• Denial of Service or situations where the site and application are not responding

Reporting a Vulnerability

Netskope accepts vulnerability reports via below channels –

• Through BugCrowd (www.bugcrowd.com). If BugCrowd is not open or available please share any vulnerabilities with [email protected] and Netskope will work to get you recognition via BugCrowd when it becomes available.
• Directly to Netskope via email using [email protected]

Note: Netskope does not support PGP-encrypted emails. For particularly sensitive information,we ask that you submit through the Netskope’s BugCrowd program. Reports may be submitted anonymously.

Netskope prefers reports via BugCrowd but will respond to reports through any of the above channels. Note, only the reports submitted via BugCrowd will be eligible for bounties, except in the event that BugCrowd is not open or available, as noted above.

Reports should include:

• Description of the location and potential impact of the vulnerability.
• A detailed description of the steps required to reproduce the vulnerability. Proof of concept (POC) scripts, screenshots, and screen captures are all helpful. Please use extreme care to properly label and protect any exploit code.
• Any technical information and related materials Netskope would need to reproduce the issue.
• Associated CWEs and Risk Rating such as Base CVSS (if applicable).

Please keep vulnerability reports current by sending Netskope any new information as it becomes available.

Note: Netskope may share your vulnerability reports with US-CERT, as well as any affected vendors or open source projects.

Coordinated Disclosure

Netskope is committed to patching vulnerabilities in a timely manner based upon the severity of the vulnerability and disclosing the details of those vulnerabilities when patches are published. Netskope knows that public disclosure of vulnerabilities can be an essential part of the vulnerability disclosure process and that one of the best ways to make software better is to enable everyone to learn from each other’s mistakes.

At the same time, disclosure in absence of a readily available patch may increase risk rather than reduce it, and so Netskope asks that you refrain from sharing your report with others while Netskope works on a patch. If you
believe there are others that should be informed of your report before the patch is available, please let us know so Netskope may consider other arrangements.

Netskope recognizes that self-disclosure of bugs may be of interest to you and does not take issue with this practice. Netskope asks that any self-disclosure publication be coordinated with the release of required patches
and in conjunction with Netskope’s advisory communications efforts. Note that in some cases there may be sensitive information that Netskope will require you to redact, so please review with Netskope before self-disclosing.

Questions

For any questions on the policy and for further help, please write to us at [email protected].

Note: Netskope reserves the right to update the policy at any time.