<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Risk-Scoring on CuraSec</title><link>https://curasec.metacog.co.kr/tags/risk-scoring/</link><description>Recent content in Risk-Scoring on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Sep 2026 13:51:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/risk-scoring/index.xml" rel="self" type="application/rss+xml"/><item><title>vulnometry: business-context vuln scoring over NVD/EPSS/KEV</title><link>https://curasec.metacog.co.kr/insights/2026-09-05-san3ncrypt3d-vulnometry-55/</link><pubDate>Sat, 05 Sep 2026 13:51:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-05-san3ncrypt3d-vulnometry-55/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Interesting approach to contextualizing CVE severity with business exposure signals; worth evaluating whether it improves triage prioritization over raw EPSS/KEV alone, but no immediate action required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Business-weighted vulnerability scoring aligns with risk-register thinking; worth flagging to engineering teams as a potential framework for communicating patch priority in business terms to leadership.&lt;/li>
&lt;/ul></description></item></channel></rss>