Securing Claude Code: The New Compliance API, Local Visibility, and Identity Governance
Anthropic introduced new Compliance API endpoints (as of August 11, 2026) providing visibility into local Claude Code sessions, including session metadata and full transcripts of model interactions Local AI agents account for 68.6% of AI agents discovered in customer environments, inheriting employee credentials, network position, and permissions Claude Code operates as a hybrid system where the LLM (brain) runs in Anthropic's cloud while the harness (hands) executes commands locally on endpoint
Analysis
TL;DR
- Anthropic introduced new Compliance API endpoints (as of August 11, 2026) providing visibility into local Claude Code sessions, including session metadata and full transcripts of model interactions
- Local AI agents account for 68.6% of AI agents discovered in customer environments, inheriting employee credentials, network position, and permissions
- Claude Code operates as a hybrid system where the LLM (brain) runs in Anthropic's cloud while the harness (hands) executes commands locally on endpoints, creating a governance gap
- Three-layer governance model is needed: managed settings (policy baseline), Compliance API (activity logging), and endpoint telemetry (local execution context)
- Static allow/deny policies and activity logs alone are insufficient; logs cannot determine whether an agent's access is legitimate, requiring integration of identity, intent, and credentials
Why It Matters
This represents a fundamental shift in AI security as agents move from browser-based interfaces to local endpoints, challenging traditional shared-responsibility models and centralized monitoring approaches. The article exposes a critical governance gap: organizations can now see what local AI agents do, but cannot easily determine if those actions are authorized or legitimate, requiring new security frameworks that combine cloud-side telemetry with endpoint-side context.
Technical Details
- Compliance API Endpoints: Three new endpoints introduced on August 11, 2026 —
GET /v1/compliance/apps/sessions/local(session metadata list),GET /v1/compliance/apps/sessions/local/{session_id}(individual session metadata), andGET /v1/compliance/apps/sessions/local/{session_id}/messages(full transcript) - Managed Settings: JSON files on Mac/Linux and registry records on Windows that enforce organizational policy baselines, with precedence over global, project, and user settings; supports allow/deny lists for MCP servers, regex patterns for bash commands, and skill command restrictions
- Three-Layer Governance Architecture: Layer 1 (Managed Settings for policy baseline), Layer 2 (Compliance API for cloud-side transcript visibility), Layer 3 (Endpoint telemetry for local process/file/configuration data that cloud services cannot observe)
- Transcript Block Types: Logs capture three block types — text, tool_use, and tool_result — covering user prompts, bash commands, file reads/writes, and MCP commands; the model holds no server-side state, so the harness resends full context each turn
- Survey Data: Token Security found local agents represent 68.6% of AI agents in customer environments; Cloud Security Alliance survey of 418 IT/security professionals showed 68% rated visibility as high while 82% discovered unknown agents
Industry Insight
- Organizations must adopt a hybrid governance strategy combining Anthropic's Compliance API with endpoint detection and response (EDR) tools, as neither alone provides complete visibility — EDR offers evidence but cannot connect activity to owner intent and credentials
- The traditional SaaS centralized monitoring model is insufficient for endpoint AI agents; security teams should expect increased administrative burden and invest in identity governance frameworks that can correlate cloud-side transcripts with endpoint-side execution context
- Static policy enforcement (allow/deny lists, regex patterns) will prove inadequate for the pace of AI-driven workflows; organizations should plan for dynamic, context-aware governance solutions that can assess legitimacy rather than merely logging activity
Disclaimer: The above content is generated by AI and is for reference only.