<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spoiledlunch</title><link>https://511d98a7.spoiledlunch.pages.dev/</link><description>Nerdy Stuff. Tech Talk. Zero Freshness. Analysis and commentary on GRC, security, and AI.</description><generator>Hugo 0.160.1</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 17:05:00 -0400</lastBuildDate><atom:link href="https://511d98a7.spoiledlunch.pages.dev/tags/vulnerability-management/" rel="self" type="application/rss+xml"/><item><title>Why Vulnerability Management Breaks Long Before Patching Does</title><link>https://511d98a7.spoiledlunch.pages.dev/articles/2026-04-28-why-vulnerability-management-breaks-long-before-patching-does/</link><pubDate>Tue, 28 Apr 2026 17:05:00 -0400</pubDate><guid>https://511d98a7.spoiledlunch.pages.dev/articles/2026-04-28-why-vulnerability-management-breaks-long-before-patching-does/</guid><description>Article • April 28, 2026 • 7 min read | Topics: Security | When leaders say their vulnerability program is struggling because patching is too slow, they are usually describing the last visible failure, not the first one.
Patching is where the program becomes …</description><author>Spoiledlunch</author><category>Security</category><category>vulnerability management</category><category>patching</category><category>asset inventory</category><category>prioritization</category></item></channel></rss>