<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vuln-Management on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vuln-management/</link><description>Recent content in Vuln-Management on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 12 Oct 2026 20:16:55 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vuln-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Opinion: Vulnerability reports have lost their special status</title><link>https://curasec.metacog.co.kr/insights/2026-10-12-vulnerability-reports-are-not-special-anymore/</link><pubDate>Mon, 12 Oct 2026 20:16:55 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-12-vulnerability-reports-are-not-special-anymore/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Filippo Valsorda&amp;rsquo;s analysis on how the commoditization of CVEs and bug bounties has changed how vuln reports should be weighted — useful context for refining your own triage and prioritization process, but no immediate system change required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A practitioner-level perspective on why vulnerability disclosure signals have become noisier — relevant background for setting expectations with boards and customers about how your team triages the flood of CVE communications.&lt;/li>
&lt;/ul></description></item></channel></rss>