Notifications
Clear all
Topic starter
22/06/2026 4:55 pm
TL;DR: Agentic identity spans three distinct layers, discovery and posture, directory and lifecycle governance, and per-action proof, and no single product covers all of them, according to Scramble ID. The governance assumption that one control plane can both authorise and evidence autonomous actions is already breaking down as agent estates grow.
NHIMG editorial — based on content published by Scramble ID: The Agentic Identity Stack: Where Okta, Microsoft Entra, Astrix, Oasis, and ScrambleID Fit Together
By the numbers:
- Gartner expects 40% of enterprise applications to ship task-specific AI agents by the end of 2026, up from under 5% in 2025.
Questions worth separating out
Q: How should security teams govern agentic identity without relying on one platform?
A: Use a layered model. Discovery finds agents and related NHIs, directory governance controls ownership and lifecycle, and per-action proof preserves evidence for high-impact actions. That separation prevents one tool from being overloaded with inventory, authorisation, and non-repudiation requirements at the same time.
Q: Why do agentic systems need proof of action as well as access control?
A: Access control can say an agent was allowed to act, but it cannot on its own prove what the agent actually did under that authority.
Q: What breaks when discovery, lifecycle, and audit are forced into one control plane?
A: The programme usually ends up with gaps in one of three places: incomplete inventory, weak ownership and deprovisioning, or evidence that does not stand up to scrutiny.
Practitioner guidance
- Map agentic controls to three ownership layers Assign discovery, lifecycle governance, and per-action proof to separate operational owners so no team assumes a control it cannot actually deliver.
- Inventory shadow agents and MCP servers first Build a complete inventory of sanctioned and unsanctioned agents, connected tools, and related non-human identities before expanding governance.
- Separate lifecycle approval from action evidence Treat owner approval, scope assignment, and deprovisioning as directory functions, then require cryptographic evidence for high-impact actions such as payments, approvals, or deletions.
What's in the full article
Scramble ID's full article covers the operational detail this post intentionally leaves for the source:
- Layer-by-layer product mapping showing how directory, posture, and proof controls fit together in practice
- Specific examples of how agent directories, discovery tools, and cryptographic proof differ in governance scope
- Framework references and market context that explain why buyers are treating agentic identity as a stack
- Implementation detail on when per-action authority and hash-chain evidence become necessary
👉 Read Scramble ID's analysis of the agentic identity stack →
Agentic identity stack: what IAM teams need to govern first?
Explore further
22/06/2026 5:05 pm
Agentic identity is not a single control problem. The market is splitting into discovery, governance, and proof because those layers solve different identity questions. Discovery tells you what exists, lifecycle governance tells you what is allowed to act, and per-action proof tells you what actually happened. That separation will shape how procurement, architecture, and audit teams divide responsibility, so practitioners should stop shopping for a one-layer answer.
A few things that frame the scale:
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to the Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: How do IAM and NHI teams decide which agent actions need stronger controls?
A: Start with impact. Actions that move money, approve transactions, alter records, or trigger external obligations should receive lifecycle controls plus cryptographic evidence. Low-risk actions can stay in normal monitoring, but the classification must be explicit before agents are allowed to scale.
👉 Read our full editorial: Agentic identity is a three-layer stack, not one product
