<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevSecOps on PeteMahon.net</title><link>https://petemahon.net/tags/devsecops/</link><description>Recent content in DevSecOps on PeteMahon.net</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Tue, 24 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://petemahon.net/tags/devsecops/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Build Pipeline is a Target: A CI/CD Security Checklist</title><link>https://petemahon.net/posts/cicd_checklist_trivy/</link><pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate><guid>https://petemahon.net/posts/cicd_checklist_trivy/</guid><description>&lt;h2 id="why-you-should-care-even-if-you-dont-know-what-cicd-is"&gt;Why You Should Care (Even If You Don&amp;rsquo;t Know What CI/CD Is)&lt;/h2&gt;
&lt;p&gt;If your organisation builds software — or relies on software built by others (which is everyone) — there&amp;rsquo;s a factory floor somewhere that assembles it. That factory floor is your CI/CD pipeline. CI/CD stands for Continuous Integration / Continuous Delivery, and it&amp;rsquo;s the automated process that takes code written by developers, tests it, packages it, and ships it out to wherever it needs to go.&lt;/p&gt;</description></item></channel></rss>