<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Secure Development on Nalar</title>
    <link>https://nalar.dev/tags/secure-development/</link>
    <description>Recent content in Secure Development 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/secure-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop Secrets Before They Enter Version Control</title>
      <link>https://nalar.dev/stop-secrets-before-they-enter-version-control/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/stop-secrets-before-they-enter-version-control/</guid>
      <description>&lt;p&gt;A developer can remove an API key from the latest version of a file and still leave the key in version-control history. Once a real credential has been committed, deleting the visible line is therefore not enough: copies may remain in earlier commits, clones, caches, mirrors, build systems, or other places that observed the repository.&lt;/p&gt;&#xA;&lt;p&gt;This makes secret leakage a good problem to stop early. Instead of relying only on a later scan that reports credentials after they have entered repository history, a team can inspect changes at the boundary where they are about to be accepted and block likely secrets before that happens.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
