<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Integrity on Nalar</title>
    <link>https://nalar.dev/tags/data-integrity/</link>
    <description>Recent content in Data Integrity on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/data-integrity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Authenticated Encryption for Data You Must Trust</title>
      <link>https://nalar.dev/use-authenticated-encryption-for-data-you-must-trust/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/use-authenticated-encryption-for-data-you-must-trust/</guid>
      <description>&lt;p&gt;Encrypting sensitive data can hide its contents while still leaving an important question unanswered: &lt;strong&gt;has the encrypted data been changed?&lt;/strong&gt; If an application decrypts modified ciphertext without a reliable integrity check, it may consume attacker-influenced plaintext even though the attacker never learned the encryption key.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters anywhere decrypted data affects a security decision, a payment amount, a permission, a destination, or another meaningful application state. Confidentiality answers who can read the data. Integrity answers whether the protected data is the same data that an authorized key holder produced.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
