Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

Vault’s seal and unseal mechanism protects your data at rest by ensuring the encryption key is only accessible in memory when explicitly unlocked. Every time Vault starts, it launches in a sealed state. In this state, Vault knows where your data resides (via its configured storage backend) but cannot decrypt it until the master key is reconstructed.

​
Vault Sealed State

When Vault is sealed:
  • Only vault status and the unseal operation are permitted.
  • All other actions—reading or writing secrets, generating tokens, etc.—remain blocked.
Unsealing Vault reconstructs the master key, decrypts the in-memory encryption key, and allows normal operations. Sealing removes the encryption key from memory, requiring a fresh unseal to resume.
The image is a slide titled "Seal and Unseal," explaining the concept of sealing a Vault, which involves discarding the encryption key and requiring an unseal for further operations. It lists reasons for sealing, such as key exposure, network intrusion detection, and malware presence.

​
Why Seal Vault Manually?

Common reasons to seal Vault immediately include:
  • Suspected exposure of unseal key shards (e.g., accidentally published in a public repo)
  • Departure or unavailability of key-holding personnel
  • Detection of network intrusion
  • Malware or spyware discovered on Vault nodes
If unseal key shards are compromised or lost, Vault cannot decrypt the data at rest until a valid threshold of shards is provided. Store and distribute shards securely.

​
Sealing & Unsealing Methods

Vault supports three primary unseal mechanisms:
MethodDescriptionExample Providers
Key ShardingDefault Shamir’s Secret Sharing splits the master key into N shares with a threshold.n=5 shares, threshold=3
Cloud Auto UnsealIntegrates with a cloud KMS to auto-unseal on startup.AWS KMS, Azure Key Vault
Transit Auto UnsealUses a remote Vault (transit cluster) to protect and unseal the master key.Vault Transit Secrets Engine (remote cluster)
The image illustrates three options for sealing and unsealing: Key Sharding (Shamir), Cloud Auto Unseal, and Transit Auto Unseal, each represented with distinct icons and colors.
When Vault is initialized, the master key is split into multiple key shards using Shamir’s Secret Sharing. For example, Vault might create 5 shards with a threshold of 3. Each shard is handed to a different trusted individual. To unseal:
  1. Provide at least the threshold number of shards.
  2. Vault combines them to reconstruct the master key.
  3. The master key decrypts the encryption key in memory, and Vault transitions to an unsealed state.
The image illustrates the process of unsealing with key shards using Shamir's Secret Sharing Algorithm, showing how key shards combine to form a master key, which then protects an encryption key and vault data.

​
Step-by-Step Demo

  1. Verify sealed status: 
    vault status
# Key                Value
# ---                -----
# Seal Type          shamir
# Sealed             true
# Total Shares       5
# Threshold          3
# Unseal Progress    0/3
  2. Submit two shards (order doesn’t matter): 
    vault unseal <key-shard-1>
# Unseal Progress: 1/3

vault unseal <key-shard-2>
# Unseal Progress: 2/3
  3. Provide the third shard: 
    vault unseal <key-shard-3>
# Key                Value
# ---                -----
# Seal Type          shamir
# Sealed             false
# Total Shares       5
# Threshold          3
# Version            1.7.0
# Storage Type       consul
# Cluster Name       vault-cluster
# Cluster ID         xxx-xxx-xxx-xxx
# HA Enabled         true
Once unsealed, Vault displays runtime and cluster details and begins serving requests.

​
Best Practices for Key Shards

The image is a slide titled "Unsealing with Key Shards," detailing guidelines for securely managing key shards, including distribution among employees and encryption practices.
  • Separate custody: Distribute shares so no single person holds the threshold.
  • Encrypt at rest: Supply PGP public keys during initialization to encrypt each shard.
  • Offline storage: Keep shards out of online systems and automated backups.
  • Balance threshold: A higher threshold boosts security but may affect availability.
Preparing PGP keys for shard encryption helps ensure that only the intended recipient can decrypt their shard.

Watch Video