<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Runtime-Security on CuraSec</title><link>https://curasec.metacog.co.kr/tags/runtime-security/</link><description>Recent content in Runtime-Security on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 04 Nov 2026 18:40:06 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/runtime-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Agent Runtime Security Gaps When AI Agents Bypass Enterprise Gateways</title><link>https://curasec.metacog.co.kr/insights/2026-11-04-radio-with-no-radar-why-agent-runtime-security-fails-without/</link><pubDate>Wed, 04 Nov 2026 18:40:06 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-11-04-radio-with-no-radar-why-agent-runtime-security-fails-without/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The architectural gap described — AI agents that never route through an enterprise-owned gateway — is worth internalizing when designing or evaluating agent deployments, but no specific vulnerability or patch action is present here.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> The scenario of employees triggering AI-powered automations outside any enterprise control plane is a real governance gap worth factoring into AI usage policy, though this piece reads as vendor-influenced thought leadership with no independent corroboration.&lt;/li>
&lt;/ul></description></item></channel></rss>