<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity-Governance on CuraSec</title><link>https://curasec.metacog.co.kr/tags/identity-governance/</link><description>Recent content in Identity-Governance on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 31 Aug 2026 18:00:29 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/identity-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Anthropic launches Compliance API for Claude Code activity visibility</title><link>https://curasec.metacog.co.kr/insights/2026-08-31-securing-claude-code-the-new-compliance-api-local-visibility/</link><pubDate>Mon, 31 Aug 2026 18:00:29 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-31-securing-claude-code-the-new-compliance-api-local-visibility/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If your team uses Claude Code, evaluate the new Compliance API endpoints to gain audit visibility into agent file access and shell execution; assess whether existing credential scoping adequately limits what the agent can reach on developer machines.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Useful framing on the detection gap for AI coding agents: activity logs show what happened but not whether access was authorized — worth factoring into coverage planning for agentic tooling in your estate.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> AI coding agents operating under developer credentials represent an emerging identity-governance gap; use this as a prompt to define a policy on agentic tool use before adoption outpaces oversight.&lt;/li>
&lt;/ul></description></item></channel></rss>