Notifications
Clear all
Topic starter
28/08/2026 12:04 pm
TL;DR: Claude’s enterprise auth centralizes human login through existing directory groups, but it does not distinguish what an agent did on a person’s behalf or give autonomous agents a separate identity, according to Aembit. The real governance gap is identity attribution and short-lived credential issuance for agent actions, not just connector authentication.
NHIMG editorial — based on content published by Aembit: Does Claude's enterprise auth already secure agent access?
By the numbers:
- Only 5.7% of organisations have full visibility into their service accounts.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: What breaks when AI agent actions are logged only under the human user's identity?
A: The audit trail loses actor distinction, which means access reviews cannot prove whether the human or the agent performed the action.
Q: How should security teams implement short-lived credentials for AI agents?
A: Start by issuing the smallest workable token lifetime for each agent class, then verify that revocation, refresh, and logging operate across every system the agent can touch.
Practitioner guidance
- Separate human login from agent attribution Require a distinct agent identity record whenever software acts on behalf of a person, so audit trails can show both the sponsor and the executor.
- Issue short-lived, policy-scoped credentials Replace stored secrets in agent runtime and MCP server configs with request-time credentials that expire with the task.
- Log delegation chains into SIEM Capture the agent identity, the human identity behind it, the target system, and the policy decision in a single event record, then forward it to SIEM for review and correlation.
What's in the full article
Aembit's full post covers the operational detail this analysis intentionally leaves at the control-design level:
- How Claude enterprise auth maps to human login while leaving agent attribution unresolved
- How runtime attestation and blended identity work across human-sponsored and autonomous agent activity
- How short-lived credentials replace stored secrets in agent and MCP runtime paths
- How access logs are structured for SIEM review when both the agent and the human must be visible
👉 Read Aembit's analysis of Claude agent identity, auth, and audit trails →
Claude agent identity: are your auth and audit controls enough?
Explore further
28/08/2026 12:04 pm
Human login control is not the same as agent governance: Directory-backed enterprise auth can tell you which person entered the system, but it cannot on its own prove what the agent did afterward. That gap matters because delegated AI access creates a second actor inside the session, and IAM controls that collapse the two into one identity lose audit integrity. The practitioner conclusion is simple: authentication without attribution is not enough for agentic access.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 79% of organisations have experienced secrets leaks, and 77% of those incidents caused tangible damage.
A question worth separating out:
Q: How do gateway controls differ from identity controls in agent access governance?
A: Gateway controls decide where traffic can go, but identity controls decide who or what is authorised to act and under what policy. Both are useful, but only identity controls can preserve accountability, attribution, and reviewability for delegated AI actions. Teams need both layers, not one in place of the other.
👉 Read our full editorial: Claude agent identity needs separate audit trails and credentials
