Trust and Security
Security starts at the foundations


The best security isn’t added on, it’s embedded
We understand the trust our clients place in us and take this responsibility seriously. When our system is the foundation of our clients’ systems, or of the solutions they build for their clients, it is critical that our software is secure, our practices are documented, and our compliance posture is accurate.
Key features
-
Isolation by design
KOS is built on seL4, the world’s most rigorously proven microkernel. Every component runs in its own address space with only the capabilities it was explicitly granted.
Read more -
Verified foundations
When critical workloads rely on a system, its security should be something you can reason about from first principles, not infer from a track record. Formal verification is how we meet that bar.
-
Open by commitment
We tell our customers what we know, when we know it. As our products reach more customers and more regulated environments, we will publish security bulletins and advisories so that anyone who runs Kry10 software can see what we have found, what it means, and what to do.

How we use data
We collect only the personal data we need to run our business and deliver our products
Contact details for customers and prospects, developer portal account information, support correspondence, and the technical data (telemetry, diagnostics) described in our Privacy Policy. We do not sell personal data.
Where we use third-party AI providers to help triage or draft responses to you, those providers operate under data processing agreements with model training disabled and data retention protections enabled. For the full picture, the categories of data we hold, the legal bases on which we hold them, how we transfer data internationally, and how to exercise your rights, see our Privacy Policy.
Kry10's security program is designed to meet the obligations our customers face
We align our practices to industry global standards, including the NIST Cybersecurity Framework, SP 800-171, ISO/IEC 27001, and the UK NCSC’s Cyber Essentials, and we extend that posture across the full lifecycle of our products.
We proactively we identify risk early, address it at the design level where we can, and treat security findings as critical to the engineering process. We hold ourselves to the same standards we expect our customers to hold their suppliers to.
Build provenance for our products, including the dependency pinning and release-signing details that back our software supply chain, is available to customers on request as part of our contracting process.
For Kry10 OS compliance information, view our Kry10 technical specfications page.

Your privacy
Kry10 Corporation is certified under the EU-U.S. Data Privacy Framework and its UK Extension
The Kry10 Holdings operates under GDPR and the equivalent protections in each jurisdiction where our entities sit, so we will respond to data subject rights requests in a timely fashion.
To exercise your rights, or to ask a question about how we handle your personal data, contact our Privacy Officer at privacy@kry10.com or see the full Privacy Policy.
Our certifications
-
EU-U.S. Data Privacy Framework
Kry10 Corporation is certified under the EU-U.S. Data Privacy Framework and its UK Extension (see our listing on the DPF List). Kry10 Holdings and its associated entities operate in compliance with the UK GDPR, EU GDPR, and the privacy regimes of each jurisdiction where our entities operate (New Zealand, Australia, the United Kingdom, the United States).
-
CMMC Level 1
Kry10 achieved CMMC Level 1 for the handling of Federal Contract Information, affirmed in the Department of Defense SPRS on 3 September 2026. Our System Security Plan and Plan of Action & Milestones for the 17 FAR 52.204-21 / CMMC Level 1 safeguarding requirements are maintained as part of our compliance program and can be shared with contracting parties under NDA.
-
NIST SP 800-171 and ISO/IEC 27001
We align our broader information security program to NIST SP 800-171 and ISO/IEC 27001, and are pursuing Cyber Essentials certification in the United Kingdom. SOC 2 is not currently a Kry10 target; ISO/IEC 27001 is the equivalent organizational standard on our roadmap.
If a security issue is identified in a Kry10 product, we will publish an advisory describing the issue, its severity, affected versions, and available mitigations or patches
Advisories will be published on our advisories page and notified to customers through the developer portal.
Our vulnerability disclosure policy, including scope, acknowledgement and triage timelines, and safe-harbour language for good-faith researchers, is available here.
Security reports go to our security team and are triaged under our incident response process.

