<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Devsecops - Tag - vo.rs</title><link>https://vo.rs/tags/devsecops/</link><description>Devsecops - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 07 Apr 2025 08:30:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/devsecops/" rel="self" type="application/rss+xml"/><item><title>Cybersecurity by Design: Embedding Zero-Trust into Your Product Roadmap</title><link>https://vo.rs/story/cybersecurity-by-design-embedding-zero-trust-into-your-product-roadmap/</link><description>&lt;p&gt;The most expensive security review I ever sat through happened the week before launch. A pen-tester found that any authenticated user could read any other user&amp;rsquo;s records by changing one integer in a URL — the classic IDOR — and the fix touched forty endpoints because authorisation had been assumed, never checked. We shipped two weeks late and bolted on a permission layer that should have been a load-bearing wall from day one. That is the lesson behind &amp;ldquo;zero-trust by design&amp;rdquo;: the cheap moment to decide that nothing is trusted by default is &lt;em&gt;before&lt;/em&gt; you&amp;rsquo;ve written the code that trusts everything.&lt;/p&gt;</description><pubDate>Mon, 07 Apr 2025 08:30:00 +0000</pubDate></item></channel></rss>