<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Catherine Edelveis on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/catherine-edelveis/</link><description>Recent content in Catherine Edelveis 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/authors/catherine-edelveis/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></channel></rss>