Encryption at Rest for Secrets

In this lesson, you will learn how to implement Envelope Encryption to secure sensitive user data by separating the storage of your data from the keys that protect it.

The Problem with Static Encryption

If you encrypt your database using a single "Master Key," you create a massive security vulnerability: if that key is compromised, every piece of data in your database is exposed simultaneously. Additionally, rotating that master key would require you to re-encrypt every single row in your database, which is computationally expensive and risky.

How Envelope Encryption Works

Envelope encryption solves this by using a two-tiered key structure:

1. Data Encryption Key (DEK): A unique, symmetric key generated to encrypt one specific user’s data.
2. Key Encryption Key (KEK): A "Master Key" (usually stored in a secure Key Vault) used to encrypt the DEK itself.

Instead of storing the plaintext DEK, you store the encrypted DEK alongside the user’s data. When you need to read the data, you fetch the encrypted DEK, send it to your Key Vault to be decrypted by the KEK, and then use the resulting DEK to decrypt your data.

Implementation Concept

In your C# application, the flow looks like this:

// 1. Generate a one-time DEK for the user's secret
byte[] dek = GenerateRandomBytes(32); 

// 2. Encrypt the secret with the DEK
byte[] encryptedData = Encrypt(userSecret, dek);

// 3. Encrypt the DEK using the KEK (via Key Vault)
byte[] encryptedDek = _keyVaultClient.Encrypt(kekId, dek);

// 4. Save both to the database
_dbContext.UserSecrets.Add(new UserSecret {
    EncryptedData = encryptedData,
    EncryptedKey = encryptedDek
});

By doing this, even if someone dumps your entire database, they cannot read the secrets because they lack access to the KEK stored in your Key Vault. Furthermore, rotating your KEK simply requires re-encrypting the small EncryptedKey field for each user, rather than re-processing the entire EncryptedData payload.

Key Takeaway: Envelope encryption protects sensitive data by wrapping the unique Data Encryption Key inside an encrypted envelope, ensuring your primary security keys never need to be stored in the database.