<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Access-Management on CuraSec</title><link>https://curasec.metacog.co.kr/tags/access-management/</link><description>Recent content in Access-Management on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 16:48:49 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/access-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Persistent AI Coworkers Expose Gaps in Identity Security Models</title><link>https://curasec.metacog.co.kr/insights/2026-09-30-ai-s-third-wave-coworkers-break-the-security-model-that-work/</link><pubDate>Wed, 30 Sep 2026 16:48:49 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-30-ai-s-third-wave-coworkers-break-the-security-model-that-work/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> AI agents with continuous standing access require dedicated identity lifecycle controls (scoped permissions, owners, rotation) that current IAM models weren&amp;rsquo;t built for — no patch or exploit today, but worth factoring into any AI-integrated platform design.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> As AI coworkers proliferate, develop an AI identity governance policy this quarter — covering credential ownership, least-privilege scoping, and lifecycle termination — before standing-access agents become an unmanaged risk in your environment.&lt;/li>
&lt;/ul></description></item></channel></rss>