Key Derivation

Definition

Key derivation is the controlled creation of one or more cryptographic keys from a source secret, shared secret, password, seed, or master key using a defined key derivation function. It can separate keys by purpose, account, protocol, or session without storing every key independently. Secure derivation requires suitable entropy, domain separation, context data, and an approved construction rather than simply hashing a secret once.

Overview

Key derivation transforms existing secret material into new keys with defined lengths and purposes. A key derivation function can extract usable entropy from an input and expand it into multiple independent outputs. Wallets may derive account keys from a seed, secure channels may derive session keys from a shared secret, and infrastructure systems may create separate encryption and authentication keys from one master secret.

Context and domain separation are essential. Labels, account paths, network identifiers, protocol versions, and usage values help ensure that two derived keys are not accidentally reused for different functions. The same source and parameters normally produce the same output, which supports deterministic recovery but also means that compromise of the source can expose every descendant key. The relationship must be evaluated against the specific derivation design.

Key derivation is not the same as Key Rotation. Derivation explains how a key is generated from existing material; rotation replaces an active key or changes which derived key is in use. It is also distinct from ordinary hashing. Approved KDFs use structured extraction, expansion, iteration, salt, or pseudorandom functions to meet a defined security goal.

Implementations should specify the KDF, hash or MAC algorithm, salt, iteration or work factor, output length, path, and context. These values must be backed up when required for recovery. Wallet and payment systems should never invent incompatible derivation paths silently, because the same seed can then produce different Account Keys across software and make funds appear inaccessible.

A sound implementation treats Key Derivation as a network-specific concept. secure key derivation uses a specified KDF, context, and domain separation to create purpose-specific keys from protected source material. For Key Derivation, versioned rules, reproducible test data, and retained evidence help prevent assumptions from one protocol or release being applied to another.

Key Takeaway

Secure key derivation uses a specified KDF, context, and domain separation to create purpose-specific keys from protected source material.

Sources

Recommendation for Key Derivation Using Pseudorandom Functions — NIST (2026-08-02)
Recommendation for Key Management: Part 1 — NIST (2026-08-02)