<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sbom on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/sbom/</link><description>Recent content in Sbom on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 14 Apr 2026 07:00:03 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/sbom/index.xml" rel="self" type="application/rss+xml"/><item><title>Modernizing Production Containers to Resist the Constant CVE Flow</title><link>https://javapro-en.svenruppert.com/modernizing-production-containers-to-resist-the-constant-cve-flow/</link><pubDate>Tue, 14 Apr 2026 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/modernizing-production-containers-to-resist-the-constant-cve-flow/</guid><description>&lt;p&gt;Common Vulnerabilities and Exposures or CVEs is a catalog of publicly disclosed software security flaws that attackers can use to gain unauthorized access.&lt;/p&gt;
&lt;p&gt;With 40,003 CVEs recorded in 2024, denoting a 39% increase as compared to 2023, container vulnerabilities are no longer a minor cleanup task. It is a river that floods Kubernetes clusters, drowning the teams in operational burden while real exposures slip through.&lt;/p&gt;
&lt;p&gt;Chasing every single CVE is a road to nowhere as new vulnerabilities are discovered constantly. The solution is to build a centralized vulnerability management system that will serve as a dam resisting the CVE flood and enable controlled CVE identification and remediation. &lt;/p&gt;</description></item><item><title>How to Containerize a Java Application Securely</title><link>https://javapro-en.svenruppert.com/how-to-containerize-a-java-application-securely/</link><pubDate>Thu, 03 Jul 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/how-to-containerize-a-java-application-securely/</guid><description>&lt;h2 id="tldr"&gt;TL;DR&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Containerization&lt;/strong&gt; or &lt;strong&gt;Dockerization&lt;/strong&gt; is the process of packaging an application and its dependencies into a Docker image.&lt;/li&gt;
&lt;li&gt;It&amp;rsquo;s beneficial to containerize your Java application as it provides a consistent environment for development, testing, and deployment.&lt;/li&gt;
&lt;li&gt;Java is a compiled language, so your Docker image will only contain the compiled Java bytecode and the Java runtime environment.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Supply-chain security&lt;/strong&gt; is the process of checking the dependencies in your application for vulnerabilities.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SBOM&lt;/strong&gt; (Software Bill of Materials) is a list of all the dependencies in your application.&lt;/li&gt;
&lt;li&gt;It&amp;rsquo;s a good practice to generate an SBOM when building your Docker image and push it to a registry for later reference.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="technical-requirements"&gt;Technical Requirements&lt;/h2&gt;
&lt;p&gt;In this article, we will use the following tools:&lt;/p&gt;</description></item></channel></rss>