<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Key Management on Nalar</title>
    <link>https://nalar.dev/tags/key-management/</link>
    <description>Recent content in Key Management on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/key-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Protect Encryption Keys with Envelope Encryption</title>
      <link>https://nalar.dev/protect-encryption-keys-with-envelope-encryption/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/protect-encryption-keys-with-envelope-encryption/</guid>
      <description>&lt;p&gt;Encrypting sensitive data is only useful if the keys are protected as carefully as the data itself. A common mistake is to focus on the encryption algorithm while treating key storage as a secondary detail. If an attacker can obtain both the ciphertext and the key that decrypts it, the encryption no longer provides the intended protection.&lt;/p&gt;&#xA;&lt;p&gt;Envelope encryption addresses this operational problem by using different keys for different jobs. A &lt;strong&gt;data encryption key&lt;/strong&gt; encrypts the data, while a separate &lt;strong&gt;key-encryption key&lt;/strong&gt; protects the data key. This separation makes it possible to encrypt many pieces of data without storing their plaintext data keys beside them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
