<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Risk-Prioritization on CuraSec</title><link>https://curasec.metacog.co.kr/tags/risk-prioritization/</link><description>Recent content in Risk-Prioritization on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 11 Sep 2026 14:58:57 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/risk-prioritization/index.xml" rel="self" type="application/rss+xml"/><item><title>Prioritize Exploitable Attack Paths Over Raw CVE Severity Scores</title><link>https://curasec.metacog.co.kr/insights/2026-09-11-your-critical-vulnerabilities-might-not-be-your-biggest-risk/</link><pubDate>Fri, 11 Sep 2026 14:58:57 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-11-your-critical-vulnerabilities-might-not-be-your-biggest-risk/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Reinforces the case for context-aware vuln prioritization — accounting for network segmentation and identity controls when triaging scanner output — but introduces no new tooling or immediate remediation action.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Supports the argument that raw scanner counts are a poor board metric; useful framing for shifting reporting toward exploitability-weighted risk posture in future program reviews.&lt;/li>
&lt;/ul></description></item></channel></rss>