<?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 blobstreaming</title><link>https://blobstreaming.org/topics/security/</link><description>Recent content in Security on blobstreaming</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Apr 2026 04:47:00 +0000</lastBuildDate><atom:link href="https://blobstreaming.org/topics/security/index.xml" rel="self" type="application/rss+xml"/><item><title>DevSecOps in Practice: Integrating Security into CI/CD (2026)</title><link>https://blobstreaming.org/notes/devsecops-in-practice-2026/</link><pubDate>Sat, 18 Apr 2026 04:47:00 +0000</pubDate><guid>https://blobstreaming.org/notes/devsecops-in-practice-2026/</guid><description>&lt;p>DevSecOps is the principle that security testing belongs in the CI/CD pipeline, not in a quarterly audit. The idea is simple. The execution is where most teams struggle — either the security checks are so slow they block deployments, so noisy they get ignored, or so disconnected from the developer workflow that nobody acts on the results.&lt;/p></description></item></channel></rss>