Citizen Records and the Question of Who Can Actually Decrypt Them

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

This is not a hypothetical concern for an agency moving citizen records through third-party platforms. A locked archive 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 government agencies, why it is the detail most security reviews skip, and what genuine customer-owned key management requires in practice, down to who can rotate the key and on what timeline.

Executive Summary

Security reviews of government platforms often stop at encryption algorithm and key length, as if AES-256 automatically means citizen data is safe. 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 agency’s behalf, that vendor retains the technical ability to read citizen records at any time, for any reason, including a reason the agency never agreed to and its own citizens never consented to. Customer-owned key management, backed by hardware, removes that ability entirely. For public sector IT leaders, this reframes encryption from a procurement checkbox into a specific, testable architectural fact.

Key Takeaways

1. Encryption only protects data from parties who do not hold the key. A vendor-held key means citizen data protection depends on the vendor’s willingness, not the encryption itself.
2. 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 described in a procurement document.
3. A hardware security module makes key ownership a physical fact, not a policy. A key generated and stored in an agency-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. An agency that cannot rotate a key on its own timeline does not have full control over citizen data.
5. Encryption strength is irrelevant if the wrong party holds the key. The question that matters for citizen trust is who can decrypt, not how strong the cipher is.

Why Encryption Strength Is the Wrong Question for Citizen 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 citizen 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. 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, and an agency relying only on that claim has no real answer for a parliamentary inquiry.

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 agency’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 agency may never see the key at all. In a customer-owned key model, the agency 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 citizen 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. 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 an agency suspects a key may have been exposed, whether through a compromised credential or a suspected breach, the ability to rotate that key immediately, without waiting on the vendor’s release schedule, is what makes key ownership operationally meaningful.

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 an agency should be able to exercise on its own timeline rather than the vendor’s.

Building Key Custody Into Vendor Due Diligence

For a public sector IT team evaluating a vendor, the practical shift is to 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 only the first question, about algorithm and key length, has told the agency nothing about who actually controls citizen data once it is encrypted.

How a Data Control Plane Makes Key Ownership an Architectural Guarantee

The Kiteworks Data Control Plane integrates customer-owned encryption keys through a hardware security module, so that key generation and storage sit outside Kiteworks’ own reach. Agencies 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. Every action across every channel, including email, file sharing, APIs and AI agents, 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 procurement document.

Agencies 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 citizen data and compliance requirements.