<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vendor-Advisory on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vendor-advisory/</link><description>Recent content in Vendor-Advisory on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 26 Sep 2026 14:58:08 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vendor-advisory/index.xml" rel="self" type="application/rss+xml"/><item><title>Kiteworks urges global server shutdown amid imminent zero-day threat</title><link>https://curasec.metacog.co.kr/insights/2026-09-26-kiteworks-urges-6-hour-server-shutdown-over-potential-zero-d/</link><pubDate>Sat, 26 Sep 2026 14:58:08 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-26-kiteworks-urges-6-hour-server-shutdown-over-potential-zero-d/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If you run Kiteworks, follow the vendor&amp;rsquo;s emergency guidance immediately: coordinate the advised shutdown window and monitor the vendor portal for patch or mitigation details as they emerge.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Treat any Kiteworks instance in the environment as potentially targeted; heighten log monitoring on those hosts now and prepare an assume-breach sweep plan for when IOCs are published.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Confirm this week whether Kiteworks is in your environment, assess business impact of the recommended shutdown, and brief leadership before the downtime window — this vendor-issued emergency notice will likely generate customer and board questions.&lt;/li>
&lt;/ul></description></item></channel></rss>