Skip to content

Vulnerability Disclosure Policy

Welcome to Kry10 Holdings' vulnerability disclosure policy.

This policy covers how Kry10 Holdings receives, triages, and publishes information about security vulnerabilities in Kry10 products and services. It applies to Kry10 Holdings, which comprises the following legal entities (collectively referred to as Kry10, we, us or our):

Entity Jurisdiction Primary Role
Kry10 Holdings United States Parent company
Kry10 NZ New Zealand NZ operations
Kry10 Corporation United States US operations; DPF certificate holder
Kry10 Pty Ltd Australia Australian operations
Kry10 UK Ltd United Kingdom UK operations

Kry10 builds secure operating systems for critical infrastructure. We depend on the security community, our customers, and our own team to find and fix issues in our products. This policy will inform you what we commit to when you report a vulnerability, how we publish advisories to our customers, and the protections we extend to researchers who report in good faith.

Important information and who we are

Purpose of this policy

This policy aims to give you clear information on how Kry10 receives reports of suspected security vulnerabilities in our products and services, how we respond, how we communicate with reporters, and how we notify our customers. It is important that you read this policy before submitting a report so that you are aware of what is in scope, what we commit to, and the protections we extend to good-faith research.

Your duty to inform us of changes

If you have reported a vulnerability to us and your contact details change, please keep us informed so we can continue to update you through resolution.

Third-party components

Kry10 products incorporate third-party components. If a vulnerability affects an upstream component rather than Kry10’s own code, we will coordinate with the upstream maintainer and update you on the status. Vulnerabilities that exist only in a third-party component with no Kry10 impact are best reported directly to the upstream maintainer; please let us know so we can track.

2. The products and services covered by this policy

This policy covers security vulnerabilities in:

3. What is out of scope

The following are not within the scope of this policy:

4. How to report a vulnerability

Direct report

Send an email to security@kry10.com with the following:

Encrypted report

A PGP key for security@kry10.com is listed in our security.txt file at kry10.com/.well-known/security.txt. If you cannot encrypt your report, send it in plain text, we would rather know about an issue than wait.

Through the Kry10 contact form

The Security Contact Form on our Contact page routes to the same inbox and triage process as direct email.

5. How we respond

What we commit to

Stage Target
Acknowledgement of your report Within 2 business days
Initial triage and severity assessment Within 7 business days
Progress updates during remediation At least every two weeks, and at each material milestone (confirmation, scoping, fix available, release, public advisory)
Coordinated public disclosure window 90 days from acknowledgement, by default; adjustable by agreement if a fix needs longer or a customer is actively exploited

How we remediate

Once a vulnerability is confirmed and severity is assigned, we work to deliver a fix or mitigation as quickly as the complexity of the issue allows. Remediation complexity varies by product, by platform, and by the dependencies involved, so we do not publish fixed remediation SLAs. We do commit to keeping you informed on the cadence above until the issue is closed.

6. Publication of advisories

When a vulnerability is confirmed in a Kry10 product, we publish an advisory describing it, and we notify affected customers through the developer portal.

Advisories are published on our advisories page. Each advisory describes:

Kry10 is working toward CVE Numbering Authority (CNA) status. Until then, CVE identifiers are requested through MITRE.

7. Safe harbour

Kry10 will not pursue legal action against security researchers who, in good faith:

If you are unsure whether a planned action is covered by this safe harbour, email security@kry10.com and ask before you act.

8. Recognition

Kry10 does not currently operate a paid bug bounty programme. Researchers who want recognition will be credited in the relevant advisory.

9. Glossary

Coordinated disclosure means working together with the party that reported a vulnerability and the party affected by it, so that a fix or mitigation is available before details of the vulnerability are made public. Kry10 operates to a 90-day default coordinated-disclosure window from acknowledgement.

CVE (Common Vulnerabilities and Exposures) is the publicly maintained identifier system for publicly disclosed security vulnerabilities, operated under the auspices of MITRE and the CVE Programme.

CNA (CVE Numbering Authority) is an organization authorised by the CVE Programme to assign CVE identifiers for vulnerabilities in a defined scope.

Severity refers to the categorical rating (Critical, High, Medium, Low) that Kry10 assigns to a confirmed vulnerability based on exploitability and impact.

Safe harbour means Kry10’s commitment not to pursue legal action against researchers who comply with this policy. It is not a waiver of third-party rights or applicable law.

10. Security Contacts

For all vulnerability reports and questions about this policy, please contact the Director of Security for the Kry10 Holdings:

Director of Security Email: security@kry10.com

If you wish to send an encrypted report, our PGP key is listed in our security.txt file at kry10.com/.well-known/security.txt.

For privacy-related enquiries, requests, or complaints, please see our Data Privacy Policy and contact the Privacy Officer at privacy@kry10.com.

11. Compliance Verification

Kry10 reviews this policy and the underlying vulnerability management process on at least an annual basis against the commitments set out above. Reviews are led by the Director of Security and include confirmation that:

12. Changes to this policy

We keep this policy under regular review. Material changes are noted at the top of this document with the effective date. This version was last updated on 23 November 2026.

Policy owner: Clay Hamilton, Director of Security