Vulnerability Disclosure
Version 2026-11-05
Zero Medium builds security and compliance software, and we expect it to be held to the standard it holds others to. If you believe you have found a security vulnerability in any of our products or services, please tell us. We will work with you to understand it, fix it and credit you.
1. How to report
Email security@zeromedium.com. Please do not open a public issue, post on social media or contact us through sales channels about a vulnerability. Customers may also raise a support ticket on the customer portal and mark it as a security report.
Please include:
- the product and version (or the URL of the service) affected;
- what the vulnerability is and what an attacker could do with it;
- the steps to reproduce it, with any proof-of-concept code, requests or screenshots; and
- how you would like to be credited, or that you would rather not be.
Reports in English are preferred. Our machine-readable contact details are in /.well-known/security.txt.
2. What is in scope
- Keystone, including its server, console, gateway, agents and the modules, packs and workflows we publish;
- Truestone, Waystone and Sealstone;
- the customer portal and the release bundles, licences and signatures it issues; and
- this website.
Out of scope: denial-of-service and load testing, social engineering of our staff or customers, physical attacks, findings in third-party services we do not operate, and reports from automated scanners with no demonstrated impact. A vulnerability in an open-source component we ship is in scope when it affects our product as shipped; we publish whether it does (section 5).
3. What happens next
- We acknowledge your report within 3 business days.
- We confirm whether it is a vulnerability and give you our assessment of its severity (CVSS) within 10 business days.
- We keep you informed as we work on a fix, and tell you when it is released.
- We ask that you give us 90 days from your report to release a fix before you disclose it publicly. If a fix needs longer, we will explain why and agree a date with you. If the vulnerability is being actively exploited, we may both move faster.
4. CVEs and credit
We request a CVE identifier for every vulnerability in our products that affects customers, through a CVE Numbering Authority, and name it in our advisory. With your permission we credit you by name in the advisory.
5. Security advisories
Each fixed vulnerability gets an advisory, published to customers on the customer portal and sent to each customer's security contacts. An advisory names the CVE, its severity, the affected and fixed versions, and what to do. Every release carries a software bill of materials (CycloneDX) and a VEX statement saying, for each known vulnerability in a component we ship, whether our product is affected.
6. Safe harbor
Pending legal review. The wording below is a draft awaiting counsel's review and has not yet been adopted. Until it is, please contact us before testing.
If you make a good-faith effort to follow this policy, we will consider your research authorized, will not pursue or support legal action against you for it, and will not treat it as a breach of our Software Terms of Use or our Website Terms of Use. Good faith means that you:
- test only your own installation, or accounts and data you own or have permission to use;
- avoid privacy violations, data destruction and service disruption, and stop and tell us at once if you reach data that is not yours;
- do only what is needed to demonstrate the vulnerability;
- report it to us promptly and keep it confidential until it is fixed or the period in section 3 has passed; and
- do not use it for any purpose other than reporting it to us.
7. Changes
We may update this policy. The version above shows when it last changed.