<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kiteworks on CuraSec</title><link>https://curasec.metacog.co.kr/tags/kiteworks/</link><description>Recent content in Kiteworks 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/kiteworks/index.xml" rel="self" type="application/rss+xml"/><item><title>Kiteworks Alerts Customers to Imminent Attack, Requests 9-Hour Shutdown</title><link>https://curasec.metacog.co.kr/insights/2026-09-26-kiteworks-urges-customers-to-shut-down-systems-for-9-hours-o/</link><pubDate>Sat, 26 Sep 2026 14:58:08 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-26-kiteworks-urges-customers-to-shut-down-systems-for-9-hours-o/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If you run Kiteworks, follow vendor guidance to schedule the 9-hour shutdown window and review recent access and file-transfer logs for anomalous pre-incident activity before the maintenance window.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> If Kiteworks is in your environment, initiate heightened monitoring of authentication and outbound data events now, and prepare an assume-breach sweep plan for the post-shutdown window given the federal threat intelligence backing this warning.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> Confirm whether your organization uses Kiteworks (note: this vendor&amp;rsquo;s predecessor Accellion was breached in 2021 affecting dozens of enterprises), assess business continuity impact of the 9-hour outage, and brief leadership before they read about it externally.&lt;/li>
&lt;/ul></description></item></channel></rss>