<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Scanning on Romano Roth</title><link>https://romanoroth.com/en/tags/code-scanning/</link><description>Recent content in Code Scanning on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Mon, 22 May 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/code-scanning/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub DevSecOps Part 9: Vulnerability Management</title><link>https://romanoroth.com/en/blogs/github-devsecops-vulnerability-management/</link><pubDate>Mon, 22 May 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-vulnerability-management/</guid><description>&lt;p>We have spent the previous eight sessions adding scanners to our GitHub DevSecOps pipeline — SCA, SAST, container scanning, secret detection, DAST. The scanners now produce a steady stream of findings, and the question is: where do we manage them? In Part 9, Patrick Steger and I look at GitHub&amp;rsquo;s built-in Vulnerability Management — the Security Tab — and call out what it does well and what is still missing.&lt;/p></description></item></channel></rss>