<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ungoverned-Automation on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ungoverned-automation/</link><description>Recent content in Ungoverned-Automation on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 15:39:31 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ungoverned-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Opinion: Governing Employee-Built AI Workflows in the Enterprise</title><link>https://curasec.metacog.co.kr/insights/2026-10-20-what-security-teams-can-do-to-tame-wild-code/</link><pubDate>Tue, 20 Oct 2026 15:39:31 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-20-what-security-teams-can-do-to-tame-wild-code/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Illustrates the growing governance gap as employees ship AI agents and automations outside formal review; useful framing for a CISO building an AI-use policy, but no specific incident or deadline triggers a concrete action now.&lt;/li>
&lt;/ul></description></item></channel></rss>