<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI/CD on securecode.dev</title><link>https://securecode.dev/tags/ci/cd/</link><description>Recent content in CI/CD on securecode.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://securecode.dev/tags/ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Security Into CI/CD</title><link>https://securecode.dev/insights/building-security-into-ci/cd/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://securecode.dev/insights/building-security-into-ci/cd/</guid><description>&lt;p>Security controls in CI/CD often fail for one of two reasons: they trigger too late to be useful, or they create enough noise that teams stop trusting them. Good pipeline security design is less about adding more scanners and more about deciding where feedback belongs.&lt;/p></description></item></channel></rss>