<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dora on CuraSec</title><link>https://curasec.metacog.co.kr/tags/dora/</link><description>Recent content in Dora on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 22 Sep 2026 15:30:54 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/dora/index.xml" rel="self" type="application/rss+xml"/><item><title>DORA Year Two: Operational Resilience Shifts to SOC Visibility</title><link>https://curasec.metacog.co.kr/insights/2026-09-22-dora-year-two-can-your-soc-actually-see-the-attack/</link><pubDate>Tue, 22 Sep 2026 15:30:54 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-22-dora-year-two-can-your-soc-actually-see-the-attack/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> DORA&amp;rsquo;s second year shifts focus from paperwork to whether detection and logging actually meet operational resilience requirements — useful framing for assessing current coverage gaps against regulatory expectations, but no IOCs or specific detection actions are provided.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> EU financial entities subject to DORA should use this moment to formally assess whether SOC visibility and incident detection capabilities meet year-two operational expectations; consider scheduling a gap review against DORA&amp;rsquo;s threat intelligence and ICT incident reporting requirements before year-end.&lt;/li>
&lt;/ul></description></item></channel></rss>