<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vulnerability Management on Romano Roth</title><link>https://romanoroth.com/en/tags/vulnerability-management/</link><description>Recent content in Vulnerability Management on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Tue, 13 Jun 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/vulnerability-management/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub DevSecOps Part 12: Our Recommendations and Lessons Learned</title><link>https://romanoroth.com/en/blogs/github-devsecops-recommendations/</link><pubDate>Tue, 13 Jun 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-recommendations/</guid><description>&lt;p>After eleven sessions building a full DevSecOps pipeline with GitHub — covering Software Composition Analysis, License Compliance, SAST, Container Scanning, Secret Detection, DAST, Pull Requests, Scheduled Pipelines, and Vulnerability Management — Patrick Steger and I close the series with our recommendations. What works on GitHub, where the gaps are, and what we would tell anyone setting out to build the same pipeline.&lt;/p></description></item><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><item><title>GitHub DevSecOps Part 3: Software Composition Analysis with Dependabot and CRDA</title><link>https://romanoroth.com/en/blogs/github-devsecops-sca/</link><pubDate>Thu, 19 Jan 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-sca/</guid><description>&lt;p>GitHub does not ship a default SCA tool the way GitLab does. You have to combine two things: a platform feature called Dependabot and an SCA action from the Marketplace. In Part 3 of the GitHub DevSecOps series, Patrick Steger and I wire both into our pipeline — and find out the hard way that the Marketplace path is not as smooth as the slides suggest.&lt;/p></description></item><item><title>GitLab vs. GitHub: DevSecOps Pipeline</title><link>https://romanoroth.com/en/blogs/gitlab-vs-github-devsecops/</link><pubDate>Wed, 28 Dec 2022 11:25:25 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-vs-github-devsecops/</guid><description>&lt;p>by &lt;a href="https://www.linkedin.com/in/romanoroth/" target="_blank" rel="noreferrer">Romano Roth&lt;/a> and &lt;a href="https://www.linkedin.com/in/patrick-steger-ch/" target="_blank" rel="noreferrer">Patrick Steger&lt;/a>&lt;/p>
&lt;p>&lt;figure>&lt;img
 class="my-0 rounded-md"
 loading="lazy"
 decoding="async"
 fetchpriority="auto"
 alt=""
 width="1280"
 height="720"
 src="https://romanoroth.com/images/blog/gitlab-vs-github-devsecops-inline-1_hu_21f4da4944ff7974.png"
 srcset="https://romanoroth.com/images/blog/gitlab-vs-github-devsecops-inline-1_hu_21f4da4944ff7974.png 800w, https://romanoroth.com/images/blog/gitlab-vs-github-devsecops-inline-1.png 1280w"
 sizes="(min-width: 768px) 50vw, 65vw"
 data-zoom-src="https://romanoroth.com/images/blog/gitlab-vs-github-devsecops-inline-1.png">&lt;/figure>
&lt;/p>
&lt;p>This video series will show you how to build up an enterprise-ready DevSecOps Pipeline with GitLab and GitHub and compare the two platforms.&lt;/p></description></item><item><title>GitLab DevSecOps Part 12: Our Recommendations and Lessons Learned</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-recommendations/</link><pubDate>Wed, 16 Nov 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-recommendations/</guid><description>&lt;p>After eleven sessions building a full DevSecOps pipeline with GitLab — from Software Composition Analysis to Container Scanning, SAST, Secret Detection, DAST, merge request integration, and scheduled pipelines — Patrick Steger and I close the series with our recommendations. What worked, what tripped us up, and what we would tell anyone setting out to build the same pipeline today.&lt;/p></description></item><item><title>GitLab DevSecOps Part 10: How to Do a Merge Request the Right Way</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-merge-request/</link><pubDate>Wed, 02 Nov 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-merge-request/</guid><description>&lt;p>In the previous nine sessions Patrick Steger and I built a GitLab DevSecOps pipeline that runs SAST, secret detection, software composition analysis, container scanning and DAST. Useful — but only if it actually catches issues &lt;em>before&lt;/em> they reach the default branch. In Part 10 we close that loop: we wire the pipeline into Merge Requests so every change is scanned, the deltas against the default branch are visible, and approvals are required when new high or critical vulnerabilities appear.&lt;/p></description></item><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><item><title>GitLab DevSecOps Part 3: Software Composition Analysis with Gemnasium</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-sca/</link><pubDate>Wed, 17 Aug 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-sca/</guid><description>&lt;p>Your code is the small part. The libraries you pull in are the big part — and that is where most of your CVEs live. In Part 3 of the GitLab DevSecOps series, Patrick Steger and I bring up a tiny Spring Boot demo, wire it into a GitLab pipeline, and then add Software Composition Analysis with a single include line.&lt;/p></description></item></channel></rss>