<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Triage on Romano Roth</title><link>https://romanoroth.com/en/tags/triage/</link><description>Recent content in Triage on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 12 Oct 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/triage/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab DevSecOps Part 9: Overcoming Vulnerability Management Challenges</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-vulnerability-management/</link><pubDate>Wed, 12 Oct 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-vulnerability-management/</guid><description>&lt;p>After eight sessions of adding scanners to our GitLab pipeline — SAST, secret detection, SCA, license compliance, container scanning, DAST — we now have a different problem. We have hundreds of vulnerability findings. In Part 9, Patrick Steger and I look at GitLab&amp;rsquo;s built-in Vulnerability Management: what it gives you, where it falls short, and how to actually triage findings without losing your mind.&lt;/p></description></item></channel></rss>