What CUI Protection Actually Requires From Key Custody

Every platform vendor serving defence contractors says CUI is encrypted. That claim hides the detail that actually determines protection: who holds the key. If the vendor holds it, encryption protects controlled data from outsiders and does nothing to protect it from the vendor itself, or from anyone who can lawfully compel that vendor to decrypt.

This is not a hypothetical concern for a contractor moving export-controlled technical data through third-party platforms. A locked cabinet means nothing if the vendor keeps a spare key and hands it over the moment a foreign authority asks. This article looks at what key custody actually changes for defence contractors, why it is the detail most security reviews skip, and what genuine customer-owned key management requires in practice, all the way down to who can rotate the key and on what timeline.

Executive Summary

Security reviews of platforms handling CUI often stop at encryption algorithm and key length, as if AES-256 automatically satisfies export-control expectations. It does not. The question that actually determines protection is who controls the key, because whoever controls the key controls the data, encryption or not. When a vendor generates, stores and manages the key on the contractor’s behalf, that vendor retains the technical ability to read controlled technical data at any time, for any reason, including a reason the contractor never agreed to and may not learn about until well after the fact. Customer-owned key management, backed by hardware, removes that ability entirely. For programme security leads, this reframes encryption from a documentation item into a specific, testable architectural fact an assessor can verify directly during a CMMC or export-control review.

Key Takeaways

1. Encryption only protects data from parties who do not hold the key. A vendor-held key means CUI protection depends on the vendor’s willingness, not the encryption itself.
2. Bring-your-own-key models remove the vendor’s decryption capability entirely, directly supporting export-control requirements. A vendor-managed key leaves that capability fully intact regardless of the algorithm used or how it is described in a proposal.
3. A hardware security module makes key ownership a physical fact, not a policy. A key generated and stored in a contractor-controlled HSM cannot be extracted by the platform hosting the data, even under administrative access.
4. On-demand key rotation is part of genuine ownership. A contractor that cannot rotate a key on its own timeline does not have full operational control over controlled technical data.
5. Encryption strength is irrelevant if the wrong party holds the key. The question that matters for CUI is who can decrypt, not how strong the cipher is.

Why Encryption Strength Is the Wrong Question for CUI

Security reviews ask about encryption constantly, and the answers almost always describe the algorithm: AES-256 at rest, TLS 1.3 in transit. These answers are true and largely beside the point.

Encrypted Data Still Has an Owner of the Key

Every encrypted CUI file has exactly one thing standing between it and a plaintext read: the key. Whoever holds that key can read the data, decrypt it for someone else, or be compelled to decrypt it under legal process. A file encrypted with a strong cipher and a vendor-held key is not meaningfully more protected from the vendor than a file with weaker encryption, because the limiting factor in both cases is the same: the vendor can read it if it chooses to, or if it is ordered to.

Why Vendors Rarely Lead With This Distinction

Vendor documentation tends to describe encryption in terms that sound complete: “encrypted at rest and in transit using industry-standard algorithms.” This is accurate and incomplete. It says nothing about who generated the key, where it is stored, or whether the vendor’s own infrastructure has a path to it, which is exactly the gap an export-control review is designed to close.

What Customer-Owned Key Management Actually Requires

Owning a key is not a single feature so much as a chain of conditions that all have to hold. Break any link and the contractor’s control over the key becomes theoretical rather than operational.

Bring Your Own Key Versus Vendor-Managed Key

In a vendor-managed key model, the platform generates and stores the encryption key as part of its own infrastructure, and the contractor may never see the key at all. In a customer-owned key model, the contractor controls key generation and storage, typically through a hardware security module it administers or has dedicated access to. The difference is the difference between a vendor that can technically decrypt CUI and one that cannot, regardless of what either vendor’s marketing materials say about encryption strength.

Why Hardware Security Modules Matter More Than the Word Suggests

A hardware security module is a dedicated physical device built to generate, store and manage cryptographic keys in a way that resists extraction, even by someone with administrative access to the surrounding system. Integrating key management with an HSM, rather than storing keys in software alongside the application, turns key ownership from a configuration setting into a physical constraint. A software-only claim of customer key ownership can, in principle, be quietly reversed by a vendor with sufficient access to its own infrastructure. A properly integrated HSM removes that possibility by design, not by policy.

Why Rotation and Cipher Control Decide Whether Ownership Is Real

Holding a key once is not the same as controlling it continuously. Two operational details separate genuine key ownership from a claim that looks correct on a data sheet but breaks down under an assessor’s questions.

On-Demand Key Rotation

If a contractor suspects a key may have been exposed, whether through a compromised credential, a departing employee, or a suspected breach, the ability to rotate that key immediately, without waiting on the vendor’s release schedule or support queue, is what makes key ownership operationally meaningful for controlled data.

Granular Cipher and Protocol Control

The ability to enable or disable specific cipher suites and control which TLS versions are permitted is a related but separate form of control, one a contractor should be able to exercise on its own timeline rather than the vendor’s, particularly when retiring a deprecated cipher ahead of an assessment.

Building Key Custody Into Vendor Due Diligence

For a programme security team evaluating a vendor, the practical shift is straightforward to describe and easy to skip under time pressure: ask who generates the key, where it is stored, whether an HSM is involved, and who can rotate it and on what timeline. A vendor that answers all four clearly, with the contractor controlling every step, has a defensible key custody model. A vendor that answers only the first question, about algorithm and key length, has told the contractor nothing about who actually controls CUI once it is encrypted.

How a Data Control Plane Makes Key Ownership an Architectural Guarantee

Customer-owned key management only delivers on its promise when it is built into the platform’s architecture rather than offered as an add-on that most deployments skip. A Data Control Plane that treats key custody as a foundational property ensures that the vendor’s technical inability to decrypt CUI holds across every channel that data moves through, including email, file sharing, APIs and AI agents.

The Kiteworks Data Control Plane integrates customer-owned encryption keys through a hardware security module, including support for widely deployed HSM providers, so that key generation and storage sit outside Kiteworks’ own reach. Contractors retain the ability to rotate keys on demand, control which ciphers and TLS versions are enabled, and run on single-tenant architecture where that key custody is not shared with any other customer’s environment. On top of that foundation, data-aware, zero-trust controls govern every send, share and access action across every channel, and every action is captured in a tamper-proof, unthrottled audit log that feeds directly into SIEM tooling, so the key custody claim is backed by a record of enforcement rather than a line in a proposal document.

Contractors that want to test their current vendor’s key custody model against this standard can schedule a custom demo to see how customer-controlled HSM integration applies to their own CUI and export-control requirements.