<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best-Practices on netflux.io</title>
    <link>https://netflux.io/tags/best-practices/</link>
    <description>Recent content in Best-Practices on netflux.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 19:01:23 +0200</lastBuildDate>
    <atom:link href="https://netflux.io/tags/best-practices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your .env files are under attack</title>
      <link>https://netflux.io/posts/your-env-files-are-under-attack/</link>
      <pubDate>Tue, 05 May 2026 19:01:23 +0200</pubDate>
      <guid>https://netflux.io/posts/your-env-files-are-under-attack/</guid>
      <description>&lt;p&gt;Unencrypted secrets on developer workstations and long-lived credentials in continuous integration environments have&#xA;long been considered bad practice. But they have often been tolerated because the cost of avoiding them was perceived as higher than&#xA;the cost of leaving them - for most projects, most of the time. That calculation has changed. The rise of AI agents has&#xA;opened new paths for local secrets to leak, and every step of the software development lifecycle is being actively&#xA;targeted by a sustained campaign of supply chain attacks. Rigorous secrets management is now a foundational part of&#xA;every project.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
