<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cti on CuraSec</title><link>https://curasec.metacog.co.kr/tags/cti/</link><description>Recent content in Cti on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 19:07:02 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/cti/index.xml" rel="self" type="application/rss+xml"/><item><title>DisCTI: ML-Based Automated Sector Routing for Cyber Threat Intel</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-discti-who-needs-to-know-timely-automated-sector-aware-cyber/</link><pubDate>Mon, 31 Aug 2026 19:07:02 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-discti-who-needs-to-know-timely-automated-sector-aware-cyber/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The finding that 98% of MISP events lack sector tagging quantifies a real operational gap in shared CTI value; the BERT-based approach achieving F1 0.89 for sector routing is worth tracking as a future tooling direction for CTI triage workflows.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The statistic that nearly all shared CTI events go uncategorized by sector is a useful benchmark for conversations about the operational return on threat intel program investments; no action is required now, but it frames the value case for better-structured intel feeds.&lt;/li>
&lt;/ul></description></item></channel></rss>