<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Architecture on CuraSec</title><link>https://curasec.metacog.co.kr/tags/security-architecture/</link><description>Recent content in Security-Architecture on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 15:21:49 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/security-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>SANS ISC: Limit AI Agent Permissions to Shrink Blast Radius</title><link>https://curasec.metacog.co.kr/insights/2026-10-16-small-agents-smaller-blast-radius-controlling-what-ai-can-do/</link><pubDate>Fri, 16 Oct 2026 15:21:49 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-16-small-agents-smaller-blast-radius-controlling-what-ai-can-do/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Opinion piece arguing for minimal-permission AI agent design; useful mental model for engineers scoping tool access in agentic pipelines, but no immediate patch or config change required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Conceptual framing for AI agent risk governance — relevant background reading when developing an AI use policy, but no near-term decision is required.&lt;/li>
&lt;/ul></description></item></channel></rss>