<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Security - Tag - Lee Wynne</title><link>https://leewynne.com/tags/security/</link><description>Security - Tag - Lee Wynne</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 26 Mar 2026 10:40:01 +0000</lastBuildDate><atom:link href="https://leewynne.com/tags/security/" rel="self" type="application/rss+xml"/><item><title>Your DEV Credentials Shouldn't Be Able to Sink PROD</title><link>https://leewynne.com/posts/your-dev-credentials-shouldnt-sink-prod/</link><pubDate>Thu, 26 Mar 2026 10:40:01 +0000</pubDate><author>Lee Wynne</author><guid>https://leewynne.com/posts/your-dev-credentials-shouldnt-sink-prod/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/posts/dev-credentials-prod.jpg" referrerpolicy="no-referrer">
            </div><p>Most engineering teams think environment isolation means having a &ldquo;dev&rdquo; and &ldquo;prod&rdquo; flag somewhere in their deployment pipeline.</p>
<p>They&rsquo;re wrong.</p>
<p>That approach doesn&rsquo;t isolate anything, it just moves the risk around.</p>
<p>The AWS SDLC Account Pattern with Full Environment Segregation is what serious cloud architecture actually looks like. It&rsquo;s not just a best practice. It&rsquo;s the difference between teams that accidentally push breaking changes to production at 2am and teams that catch those changes before they ever leave a development branch. It&rsquo;s the difference between a breach in your DEV environment that gets contained, blast radius controlled, damage limited - and a breach in DEV that silently walks into PROD, taking customer data with it and sinking the whole ship.</p>]]></description></item></channel></rss>