<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident-Analysis on CuraSec</title><link>https://curasec.metacog.co.kr/tags/incident-analysis/</link><description>Recent content in Incident-Analysis on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 15:48:57 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/incident-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>Unsophisticated Attack Exposes Third-Party Risk at European Bank</title><link>https://curasec.metacog.co.kr/insights/2026-10-14-the-noise-inside-the-network-how-an-unsophisticated-attack-e/</link><pubDate>Wed, 14 Oct 2026 15:48:57 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-14-the-noise-inside-the-network-how-an-unsophisticated-attack-e/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Unit 42&amp;rsquo;s attack dissection may surface detection patterns and architectural weaknesses relevant to third-party integrations, but no specific CVEs, PoCs, or patch actions are indicated — worth reading to inform future design decisions around supplier access.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The full write-up likely contains TTPs and detection strategies from a real intrusion, but the summary provides no IOCs, ATT&amp;amp;CK mappings, or specific tooling details to act on immediately — review for hunting hypotheses if the sector is relevant.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A case study showing how a low-sophistication attack leveraged third-party exposure at a bank is directly applicable to vendor risk discussions and board-level risk register reviews — useful framing for upcoming supplier security reviews.&lt;/li>
&lt;/ul></description></item></channel></rss>