<?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 CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/devsecops/</link><description>Recent content in Devsecops on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 29 Oct 2026 17:12:51 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/devsecops/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab Orbit GA: graph-based vulnerability blast radius mapping</title><link>https://curadevops.metacog.co.kr/insights/2026-10-29-gitlab-orbit-find-vulnerability-blast-radius-without-the-man/</link><pubDate>Thu, 29 Oct 2026 17:12:51 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-29-gitlab-orbit-find-vulnerability-blast-radius-without-the-man/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Learn:&lt;/strong> Orbit&amp;rsquo;s graph linking code, pipelines, container images, and ownership could streamline how platform teams locate vulnerable infrastructure components during a CVE response, but it requires no change to running systems and is GitLab-specific.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> If the org is on GitLab, Orbit GA is worth noting as a DevSecOps capability that reduces manual triage overhead for security investigations — no strategic decision is forced, but it&amp;rsquo;s relevant when evaluating GitLab&amp;rsquo;s security toolchain breadth.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> GA announcement&lt;/li>
&lt;/ul></description></item></channel></rss>