<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Vulnerability-Scanning - Tag - vo.rs</title><link>https://vo.rs/tags/vulnerability-scanning/</link><description>Vulnerability-Scanning - 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>Tue, 25 Jun 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/vulnerability-scanning/" rel="self" type="application/rss+xml"/><item><title>Trivy and Container Scanning: Finding Vulnerabilities Before They Find You</title><link>https://vo.rs/story/trivy-and-container-scanning-finding-vulnerabilities-before-they-find-you/</link><description>&lt;p&gt;Every Docker image you pull is a tarball of someone else&amp;rsquo;s decisions. That base image you chose two years ago because the tutorial used it? It&amp;rsquo;s carrying an OpenSSL with a known hole, a libc with a CVE, and three system packages you&amp;rsquo;ve never heard of, one of which has a remote code execution bug filed against it. You didn&amp;rsquo;t write any of that. You&amp;rsquo;re still running it.&lt;/p&gt;
&lt;p&gt;Container scanning is the unglamorous practice of finding out what&amp;rsquo;s actually inside your images before an attacker does. And the tool I reach for first, every time, is &lt;strong&gt;Trivy&lt;/strong&gt; — partly because it&amp;rsquo;s genuinely good, and partly because it&amp;rsquo;s free, fast, and doesn&amp;rsquo;t try to drag me into a sales call.&lt;/p&gt;</description><pubDate>Tue, 25 Jun 2024 09:00:00 +0000</pubDate></item></channel></rss>