<?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 Gaurav.dev</title><link>/tags/devsecops/</link><description>Recent content in Devsecops on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/devsecops/index.xml" rel="self" type="application/rss+xml"/><item><title>DevSecOps Without Turning Delivery Into a Queue</title><link>/posts/devsecops-without-slowing-delivery/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>/posts/devsecops-without-slowing-delivery/</guid><description>&lt;p&gt;Security slows delivery when it arrives late, lacks context, or reports more noise than risk. DevSecOps works when teams receive useful feedback while a change is still cheap to fix.&lt;/p&gt;&#10;&lt;h2 id="define-what-matters"&gt;Define what matters&lt;/h2&gt;&#10;&lt;p&gt;Begin with a lightweight threat model. Identify valuable assets, trust boundaries, likely abuse, third parties, and consequences. This gives scanning and review a purpose. A public marketing site and a healthcare workflow should not share the same controls or release gates.&lt;/p&gt;</description></item></channel></rss>