Vulnerability Disclosure Policy
ZPE Systems is committed to ensuring the security of our products and services. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
This policy describes
what systems and types of research
are covered under this policy,
how to send us
vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
We encourage you to contact us to report potential vulnerabilities in our systems.
This policy is a live document and as such is subject to change without notice.
If you make a good faith effort to comply with this policy during your security research on ZPE Systems proprietary solutions and services owned or operated by ZPE Systems, we will consider your research to be authorized and we will work with you to understand and resolve the issue quickly.
You must obtain additional previous authorization from third parties before researching ZPE Systems products owned and/or operated by said third parties.
Our customers, partners, and business prospects are covered by this authorization.
ZPE Systems will not recommend or pursue legal action related to your research if you comply with this policy. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.
Under this policy, "research" means activities in which you:
Notify us as soon as possible after you discover a real or potential security issue.
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
Only use exploits to the extent necessary to confirm a vulnerability's presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
Once you've established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party),
Stop your test
Permanently delete any data you may have downloaded
Notify us immediately
Not disclose this data to anyone else
The following test methods are not authorized:
Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing.
This policy covers security vulnerabilities and concerns on ZPE Systems products
based on Nodegrid OS, ZPE Cloud managed services, and source code published by ZPE Systems, as described below.
Products based on the Nodegrid OS:
- Nodegrid Serial Console
- Nodegrid Serial Console Plus
- Nodegrid Net Services Router
- Nodegrid Gate SR
- Nodegrid Link SR
- Nodegrid Bold SR
- Nodegrid Hive SR
- Nodegrid Mini SR
- Nodegrid Manager
- Nodegrid Virtual Service Router
Cloud-based services based on these domains:
Source code published by ZPE Systems in GitHub:
Any product or service not expressly listed above, such as any connected services, as well as versions that have entered End Of Support, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any).
If you are unsure if a given system or service is within scope for this policy or not, please contact ZPE Systems via PSIRT@zpesystems.com
Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We may increase the scope of this policy over time.
Reporting a Vulnerability
We accept vulnerability reports via the
form or via
. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 2 business days.
We do not support PGP-encrypted emails. For particularly sensitive information, submit through our HTTPS web form.
What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:
Describe the location the vulnerability was discovered and the potential impact of exploitation.
Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
Write that in English, if possible.
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
We will acknowledge that your report has been received within 2 business days.
To the best of our ability, we will work to confirm the existence of the vulnerability to you within 14 days.
We will be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
Although we strive to timely address all confirmed vulnerabilities, we cannot guarantee any particular level of response.
Disclose to our current partners and customers as soon as a fix is released and to the public within 7 days after that.
Give you due credit in the public disclosure, but do not expect compensation for time and materials or vulnerabilities discovered.
We will maintain an open dialogue to discuss issues.
Questions regarding this policy may be sent to
We also invite you to contact us with suggestions for improving this policy.