<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Minimization on Nalar</title>
    <link>https://nalar.dev/tags/data-minimization/</link>
    <description>Recent content in Data Minimization 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/data-minimization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reduce Breach Impact with Data Minimization</title>
      <link>https://nalar.dev/reduce-breach-impact-with-data-minimization/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/reduce-breach-impact-with-data-minimization/</guid>
      <description>&lt;p&gt;Security controls often focus on stopping unauthorized access. That is necessary, but it leaves another useful question unanswered: &lt;strong&gt;if access controls fail, how much valuable data is available to expose?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Data minimization reduces that potential impact. The idea is simple: collect sensitive data only when there is a clear need, keep only the fields and copies that serve that need, and remove the data when the required lifetime ends.&lt;/p&gt;&#xA;&lt;p&gt;This is not a replacement for authentication, authorization, encryption, monitoring, or backups. It changes a different part of the risk equation. A system cannot leak a sensitive value that it never collected, and an old copy cannot be stolen after it has been reliably removed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
