Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Key Management and Key Rotation?

Key management covers the whole life of a cryptographic key, from generation to destruction. Rotation replaces a key on a schedule or after an incident, and is where most policies quietly fail.

Illustration for the cybersecurity term Key Management
Home / Blog / Cybersecurity Terms / What Is Key Management and Key Rotation?
17 November 2026

What Is Key Management and Key Rotation?

What Is Key Management and Key Rotation?

Encryption converts a data protection problem into a key protection problem. That is a good trade — a 32-byte secret is far easier to defend than a terabyte of records — but only if the key is actually defended. Key management is the set of processes covering a key’s entire life: how it is generated, distributed, stored, used, rotated, archived, and destroyed, and who is permitted to do each of those things.

It is the part of applied cryptography that fails most often, and the failures are rarely interesting. Keys in source control, keys in container images, keys shared between development and production, keys that nobody can identify but nobody dares delete.

The Lifecycle

  1. Generation. From a cryptographically secure source, ideally inside a hardware security module or a key management service, at the length your policy specifies.
  2. Distribution. Using a protected channel and, for high-value keys, split knowledge so no single person holds a complete key.
  3. Storage. Separated from the data the key protects, with access enforced by policy rather than by file permissions.
  4. Use. Through an authorised interface that logs every operation, with the key held in memory for as short a time as possible.
  5. Rotation. On a defined schedule, and immediately on suspicion of compromise or when a key custodian leaves.
  6. Archival. Retired decryption keys retained securely for as long as data encrypted under them still exists.
  7. Destruction. Deliberate, recorded, and irreversible — which is also a legitimate way to render data unrecoverable.

NIST SP 800-57 is the reference that most frameworks point to, and it introduces the idea of a crypto-period: the time a key may remain in use, set according to how much data it protects, how exposed it is, and how long that data must stay confidential.

What Rotation Actually Means

Organisations routinely claim annual key rotation while describing something much weaker. Three different operations get the same name:

OperationEffectEffort
Rotate the key encryption keyRe-wraps data keys; the keys protecting data are unchangedMinutes
Rotate the data encryption key for new writesNew data uses a new key; old data does notLow
Re-encrypt existing dataOld key genuinely retiredPotentially enormous

All three are legitimate, but only the third removes the old key from relevance. Envelope encryption makes this manageable by generating a fresh data key per object, so that re-encryption becomes unnecessary for the common case and the only key with a long life is the one held in hardware.

Rotation also has a cost nobody budgets for: every system that caches a key, every integration partner holding a copy, and every signed artefact referencing a key version must be considered. A rotation plan that has never been exercised is a theory, and the moment to discover its gaps is not during an incident.

What Regulators Expect

PCI DSS v4.0 is the most prescriptive. Requirements 3.6 and 3.7 cover key storage in the fewest possible locations, split knowledge and dual control for clear-text key operations, defined crypto-periods, retirement of keys when they are suspected of compromise, and signed acknowledgements from key custodians. Assessors ask for the documented procedure and the evidence that it ran.

UK GDPR is less specific but no less relevant: Article 32 expects appropriate technical measures, and the ICO’s position that encrypted data with an uncompromised key presents lower risk only holds if you can demonstrate the key was never exposed. Financial entities under DORA must evidence cryptographic key management within their ICT risk framework, including an inventory and a policy for its review. NCSC guidance on protecting bulk data takes the same line: the key management arrangements, not the algorithm, determine the real strength of the control.

The Findings We See Most

Building a key inventory is usually the most valuable first step, and it is also the prerequisite for crypto agility and for post-quantum migration. We carry out that discovery as part of our cyber risk analysis services, and the first version of the inventory almost always contains surprises.

FAQ – Frequently Asked Questions

How Often Should I Rotate Encryption Keys?

It depends on what the key protects and how exposed it is. A common baseline is annual rotation for key encryption keys, far more frequent rotation for session and ticket keys, and per-object data keys that are never reused. Rotate immediately on suspected compromise or when a custodian leaves, regardless of the schedule.

Does Rotating a Master Key Protect Old Data?

Only partially. Re-wrapping data keys under a new master key limits exposure of the wrapping key, but the keys that actually encrypt your records are unchanged, so an attacker holding one still has it. Genuine protection for existing data requires re-encryption, which is why generating a fresh data key per object is the better architecture.

Where Should Application Keys Be Stored?

In a key management service or secrets manager that the application authenticates to with a short-lived workload identity, never in source control, configuration files, environment variables baked into images, or alongside the encrypted data. For signing and root keys, use a hardware security module and mark them non-exportable.

What Is Cryptographic Erasure?

Destroying the key so that data encrypted under it becomes unrecoverable, which is often the only practical way to delete data spread across backups, replicas, and archives. It satisfies deletion requirements if the key is genuinely gone from every copy, so it depends entirely on knowing where key material has been stored.

Related Terms

You May Be Interested In These

What Is the NIST Cybersecurity Framework?

Cybersecurity Terms

17 November 2026

What Is the NIST Cybersecurity Framework?

Read More
What Are Spectre and Meltdown?

Cybersecurity Terms

17 November 2026

What Are Spectre and Meltdown?

Read More
What Is PetitPotam?

Cybersecurity Terms

17 November 2026

What Is PetitPotam?

Read More