Cloud concept · Updated

Key Custody - Key custody defines who holds cryptographic key material, where it resides, and who can control its use throughout its lifecycle.

In short

Key custody separates possession of cryptographic material from permission to administer or use a key. It matters because key generation, storage, backup, revocation, and recovery choices determine both the confidentiality and the availability of encrypted data.

Cloud Concepts Hub →

6 key aspects of Key Custody

Effective key custody makes material location, administrative authority, usage permissions, and lifecycle recovery responsibilities explicit.

01
Material possession versus administrative control

Identify separately who stores key material, who changes policies, and who can invoke cryptographic operations. A customer-managed key can still contain provider-generated material that the customer cannot export.

02
Generation and provenance

Provider-generated material reduces customer handling, while imported material allows the customer to control generation and retain an external original. Record the generation environment, approved algorithms, and authorized transfer process.

03
Storage and export boundaries

Determine whether material resides in a provider-managed HSM, a customer-controlled HSM, or an external key manager. Importing material places a copy inside the receiving service and does not imply that the service can later export it.

04
Recovery and retained copies

Protect external backups of imported material and test restoration to the intended key resource. Recovery can depend on both the original material and the continued existence of the logical key, not merely possession of the same key bytes.

05
Expiration, revocation, and destruction

Treat material expiration, material deletion, key disabling, and permanent key deletion as distinct events. Each has different recovery implications, and none automatically removes plaintext already released to consumers.

06
Operational responsibility and evidence

Assign responsibility for generation, import, rotation, monitoring, and recovery. Separate administrative and usage permissions, and retain audit records that demonstrate who performed sensitive lifecycle operations.

Cloud services for Key Custody

Key-management services provide logical key resources, authorization, and cryptographic operations, while HSM services establish hardware protection and additional customer-controlled boundaries. AWS KMS and Azure Key Vault illustrate how generation and import choices change responsibilities without necessarily changing the application-facing encryption workflow. AWS CloudHSM supports designs requiring direct HSM administration or a KMS custom key store. CloudTrail supplies audit evidence for AWS-side lifecycle actions and use. Together, these services support a custody design, but secure external backups, separation of duties, expiration monitoring, and tested recovery procedures remain explicit engineering responsibilities.

AWS CloudHSMAWS CloudHSM

AWS CloudHSM provides dedicated HSMs with customer-controlled cryptographic users and key permissions. It supports direct HSM-based key management and can back an AWS KMS custom key store, with different operational responsibilities from the default KMS key store.

AWS CloudTrailAWS CloudTrail

CloudTrail records AWS KMS API activity, supporting investigation of key imports, material deletion, policy changes, and cryptographic use. These records provide custody evidence but do not store recoverable copies of key material.

Key Custody exam questions

Real practice exam questions on Key Custody, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAP-C03

A securities exchange is migrating a message-processing application to Amazon EC2. Its trading partners require an existing protocol that encrypts messages with AES-256-GCM and transmits the ciphertext, initialization vector, and authentication tag in a prescribed format. Partners cannot accept AWS-specific ciphertext formats or change the protocol.

A regulator requires cryptographic keys and encryption operations to remain inside dedicated, single-tenant HSMs. The exchange must directly control the supported cryptographic mechanisms and key attributes. The application needs both persistent keys that survive application restarts and temporary keys for individual processing sessions. Plaintext key material must never enter EC2 instance memory. The exchange can modify its cryptographic integration and operate the required HSM infrastructure.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Deploy an AWS CloudHSM cluster and integrate the application directly through the CloudHSM PKCS #11 library. Generate nonextractable persistent token keys and temporary session keys in the HSM, and invoke its supported AES-GCM mechanism to produce the fields required by the partner protocol.

Direct CloudHSM integration gives the exchange control over supported algorithms, mechanisms, and key attributes. CloudHSM supports persistent token keys and temporary session keys. Generating nonextractable keys and performing AES-GCM operations inside the HSM keeps plaintext key material out of EC2 memory while allowing the application to assemble the required protocol format.

DVA-C02

A developer is reviewing two designs for an on-premises application that stores confidential files in Amazon S3. Design 1 uploads files over HTTPS using server-side encryption with customer-provided keys (SSE-C); the company generates and retains those keys in its on-premises vault. Design 2 uses the AWS Encryption SDK to encrypt files on premises before uploading them, with a customer managed symmetric AWS KMS key whose key material is generated by AWS KMS. The security team wants to distinguish customer control of keys from actual custody of key material. Which finding should the developer document?

Show answerCORRECT ANSWER

Design 1 sends the supplied encryption key to S3 for server-side operations. Design 2 encrypts files locally, but AWS KMS still holds the KMS key material used to protect the data keys.

SSE-C requires the client to provide the encryption key to S3 over HTTPS. S3 uses the key but does not persist it. In Design 2, file encryption occurs on premises, yet the AWS-generated wrapping key remains protected within AWS KMS. Client-side encryption therefore does not, by itself, mean that all key material remains outside AWS.

SCS-C03

A financial company is provisioning a single-Region symmetric encryption AWS KMS key with externally generated key material. A security engineer creates the KMS key with origin EXTERNAL, obtains import parameters, and wraps the approved key material with the returned wrapping public key. A mandatory approval process delays the import for 48 hours. The subsequent ImportKeyMaterial request fails because the import token has expired.

The KMS key remains in PendingImport. The company securely retains the original key material, and the existing KMS key ARN and approved key material must remain unchanged.

Which action should the engineer take to complete provisioning?

Show answerCORRECT ANSWER

Obtain new import parameters for the existing KMS key, wrap the original key material with the newly returned wrapping public key, and import it with the newly returned import token.

Import parameters are valid for 24 hours. After they expire, the engineer must obtain a new wrapping public key and import token, wrap the original material again, and submit the new wrapped material with its matching token. This preserves both the KMS key ARN and the approved key material.

Practice Key Custody in a full exam

Questions on Key Custody in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Key Custody

3 min read

Key custody describes the responsibility and technical controls surrounding cryptographic key material. A custody design identifies who generates the material, which systems hold copies, who can authorize cryptographic operations, and who can recover or destroy it. These responsibilities can belong to different parties. An organization might control access policies while a cloud provider holds the material inside hardware security modules (HSMs). Administrative control does not necessarily mean physical possession or the ability to export a key.

In cloud systems, distinguish the logical key resource from its cryptographic material. The resource carries an identifier, policies, metadata, and lifecycle settings; the material performs encryption, decryption, signing, or other operations. Calling a key customer-managed generally describes customer control over that resource, not necessarily customer generation or exclusive possession of its material.

AWS Key Management Service (AWS KMS) illustrates the difference between provider-generated and imported material. With an AWS KMS-generated symmetric encryption key, AWS KMS creates and protects the material within its managed cryptographic infrastructure. Customers authorize operations through policies and grants but cannot export that symmetric key material. This reduces the customer's responsibility for generating, transporting, and backing up the underlying material. It also means the customer cannot recover a permanently deleted KMS key by supplying an independently retained copy.

With imported material, the customer generates the material outside AWS KMS and transfers it through the supported import process, using a wrapping public key and import token obtained from AWS KMS. AWS KMS then holds a protected copy and performs authorized cryptographic operations with it. Importing therefore does not mean that the material remains outside the provider. AWS KMS cannot export the imported material back to the customer, so any required external backup must be retained securely before import.

Imported material introduces additional lifecycle responsibilities. A customer can configure an expiration time during import or choose no expiration, and can explicitly delete imported material without immediately deleting the logical KMS key. If required material expires or is deleted, operations that depend on it fail. Recovery requires restoring the matching material to the original surviving KMS key under the applicable import rules. Replacing it with unrelated material does not decrypt existing ciphertext, and retaining an external copy does not make a permanently deleted KMS key recoverable.

For example, an organization may require its security team to generate encryption material in an approved HSM and retain a protected recovery copy before importing it into a cloud key service. That design satisfies a provenance and backup requirement, but it also creates duties to protect every retained copy, monitor expiration, test restoration, and restrict import and deletion permissions. A team without those requirements may prefer provider-generated material to reduce handling and recovery risks. Rotation capabilities depend on the service, key type, and origin; do not assume identical rotation procedures for generated and imported keys.

Exclusive external custody is a different architecture from importing material. With an external key store, the external key material remains in an external key manager rather than being imported into the cloud key service. This can provide an independent control boundary, but adds network, latency, availability, and operational dependencies. In any model, separate key administrators from key users, audit sensitive operations, and test failure scenarios. Revocation blocks future operations that require the key; it does not erase plaintext or data keys already obtained by an application.

Learn Key Custody in lessons

4 short lessons on Key Custody in 3 certification courses.

Open the lessons