Patient Records Deserve Encryption Nobody Else Can Unlock
Every health IT vendor says patient data is encrypted. That claim hides the detail that actually determines protection: who holds the key. If the vendor holds it, encryption protects patient records from outsiders and does nothing to protect them from the vendor itself, or from anyone who can lawfully compel that vendor to decrypt on demand.
This is not a hypothetical concern for a health system moving special-category patient data through third-party platforms. A locked filing cabinet means nothing if the vendor keeps a spare key and hands it over the moment a request arrives. This article looks at what key custody actually changes for health systems, why it is the detail most security reviews skip, and what genuine customer-owned key management requires in practice.
Executive Summary
Security reviews of health IT platforms often stop at encryption algorithm and key length, as if AES-256 automatically means patient data is safe. It does not. The question that actually determines whether patient data is protected 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 health system’s behalf, that vendor retains the technical ability to read patient records at any time, for any reason, including a reason the health system never agreed to and may never learn about. Customer-owned key management, backed by hardware, removes that ability entirely. For health IT leaders, this reframes encryption from a compliance checkbox into a specific, testable architectural fact: can the vendor decrypt our patients’ data, or not?
Key Takeaways
- Encryption only protects data from parties who do not hold the key. A vendor-held key means patient data protection depends on the vendor’s willingness, not the encryption itself.
- Bring-your-own-key models remove the vendor’s decryption capability entirely. A vendor-managed key leaves that capability fully intact, regardless of the algorithm used or how it is marketed.
- A hardware security module makes key ownership a physical fact, not a policy. A key generated and stored in a health system’s own HSM cannot be extracted by the platform hosting the data, even under administrative access.
- On-demand key rotation is part of genuine ownership. A health system that cannot rotate a key on its own timeline after a suspected compromise does not have full control over patient data.
- Encryption strength is irrelevant if the wrong party holds the key. The question that matters for patient trust is who can decrypt, not how strong the cipher is.
Why Encryption Strength Is the Wrong Question for Patient Data
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 patient record 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. The strength of the encryption algorithm has no bearing on any of this. 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 aimed at health systems 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. A health system reading only the encryption claim, without asking the key-custody question separately, walks away with a false sense of coverage over its most sensitive data.
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 health system’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. The health system may never see the key at all. In a bring-your-own-key, or customer-owned key, model, the health system controls key generation and storage, typically through a hardware security module it administers or has dedicated access to. The difference is not cosmetic. It is the difference between a vendor that can technically decrypt patient data and one that cannot.
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 in practice.
On-Demand Key Rotation
If a health system 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. A key the health system cannot rotate on its own timeline is a key it does not fully control.
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. A health system that needs to retire a deprecated cipher ahead of a compliance deadline should not have to wait for the vendor to make that change on its behalf.
Building Key Custody Into Vendor Due Diligence
For a health IT 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 health system 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 health system nothing about who actually controls patient data 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 patient data holds across every channel that data moves through, including email, file sharing, APIs and AI agents, not just the ones a health system happened to configure carefully.
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. Health systems 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 data sheet.
Health systems 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 patient data and compliance requirements.
Frequently Asked Questions
Whoever controls the key controls the data. A vendor-held key means patient records are protected only by the vendor’s willingness or legal compulsion, not by encryption itself, regardless of whether AES-256 is used.
In a vendor-managed model, the platform generates and stores the key within its own infrastructure. In a customer-owned or bring-your-own-key model, the health system controls key generation and storage, typically via its own hardware security module, removing the vendor’s ability to decrypt data.
An HSM generates and stores keys in a dedicated physical device that resists extraction even by administrators. This turns key ownership into a physical constraint instead of a configuration setting that a vendor could reverse.
On-demand key rotation without vendor dependency and granular control over ciphers and TLS versions ensure the health system maintains continuous control, rather than relying on the vendor’s schedule or policies.