Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

Enterprise-managed authorization for AI agents: what changes now?


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 15374
Topic starter  

TL;DR: Enterprise-managed authorization moves MCP access from per-server consent into IdP-driven policy, reducing human friction while creating a path for autonomous agents to hold governed identity, according to NewCore's analysis of the MCP team and Anthropic release. The real shift is that identity can now be assigned, scoped, and revoked for agents at machine speed, not just borrowed from humans.

NHIMG editorial — based on content published by Newcore: enterprise-managed authorization for MCP and autonomous agent identity

By the numbers:

  • When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes - and as quickly as 9 minutes in some cases.

Questions worth separating out

Q: How should security teams govern AI agents that use service accounts and MCP tools?

A: Start with ownership, then add runtime attribution and containment.

Q: Why do autonomous agents break traditional consent-based access models?

A: Because consent models assume a person is present to approve access and understand the scope of the request.

Q: How can organizations effectively manage access delegation for AI agents?

A: Organizations can manage access delegation for AI agents by implementing policy-based authorization frameworks that ensure correct access levels are maintained.

Practitioner guidance

  • Classify every MCP connector by actor type Separate interactive human-on-behalf-of workflows from autonomous agent workflows before assigning authorization policy.
  • Bind agent tokens to proof-of-possession Require sender-constrained tokens for any agent that can reach sensitive tools or data.
  • Shorten token lifetime to match machine-speed use Use short-lived grants and re-request flows so access dies quickly when policy changes or the agent is decommissioned.

What's in the full article

Newcore's full blog covers the operational detail this post intentionally leaves for the source:

  • The exact ID-JAG and token-exchange flow used to move from human login to MCP authorisation.
  • The three identity models for agents, including delegated client, named actor, and agent as its own subject.
  • Implementation details for confidential clients, DPoP-bound tokens, and task-scoped RAR authorisation.
  • Examples of how the same mechanism behaves across Anthropic, Okta, Microsoft, and other early implementations.

👉 Read Newcore's analysis of enterprise-managed authorization for MCP and AI agents →

Enterprise-managed authorization for AI agents: what changes now?

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 3 months ago
Posts: 14958
 

Policy-driven consent is no longer just a human UX improvement, it is the control plane for machine identity. EMA removes the browser-mediated decision point and puts authorization inside the IdP, which is exactly where NHI governance has always wanted access decisions to live. That shifts the discussion from convenient login to authoritative lifecycle control, because revocation, audit, and scope now depend on one central policy layer. Practitioners should recognise that this is not a UI change; it is an identity architecture change.

A few things that frame the scale:

  • The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
  • Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.

A question worth separating out:

Q: Who should own revocation when an AI agent goes off task?

A: Revocation should sit with the same governance function that owns other privileged identities, because an off-task agent is still an access problem, not just an application defect. The right owner can disable the identity, remove entitlements, and review the approval path that created the risk. Shared ownership usually leaves the agent active for too long.

👉 Read our full editorial: Enterprise-managed authorization changes the identity model for AI agents



   
ReplyQuote
Share: