<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on psilva.org</title><link>https://psilva.org/tags/security/</link><description>Recent content in Security on psilva.org</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://psilva.org/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Shift-left security (and shift-left without the security part)</title><link>https://psilva.org/posts/shift-left-security/</link><pubDate>Fri, 22 May 2026 00:00:00 -0400</pubDate><guid>https://psilva.org/posts/shift-left-security/</guid><description>&lt;p&gt;If you build pipelines, own Terraform, or get pulled into release-week fire drills, you have probably heard &amp;ldquo;shift-left&amp;rdquo; in a standup, a job post, or a security review. It is not a product name. It is a way of saying: do this work earlier, while you are still in design, a PR, or CI, instead of handing it to security (or ops) at the door to production.&lt;/p&gt;
&lt;p&gt;That framing shows up a lot in DevSecOps and platform roles. This post is what people usually mean by it, plus the same idea when the topic is not security.&lt;/p&gt;</description></item></channel></rss>