Topic starter
30/07/2026 10:48 pm
TL;DR: Agentic AI removes the human from identity flows and turns every agent credential into a continuously active access point, while NHI sprawl, stale credentials, and prompt-driven tool use expand the attack surface, according to Pomerium and Rubrik Zero Labs. Static scopes and session-based controls no longer match autonomous behaviour, so governance must shift to per-action enforcement and live attribution.
Editorial analysis by NHI Mgmt Group, based on content published by Pomerium: “Identity Was Built for Humans Logging In. Agentic AI Ripped Up That Assumption.”.
By the numbers:
- Non-human identities outnumber human users by roughly 45 to 1 in the modern enterprise.
- Non-human identities can outnumber human users by as much as 100 to 1 in some organisations.
- 47% of non-human identities are more than a year old with no credential rotation.
Key questions
Q: What breaks when agentic AI inherits human-era identity controls?
A: Static scopes, session-based controls, and login-time approval all assume a person is present and intent stays stable.
Q: Why do long-lived credentials create a bigger risk for AI agents than for traditional automation?
A: AI agents can choose tools and sequence actions dynamically, so long-lived credentials become durable authority across many unpredictable requests.
Q: How can security teams tell whether action-time authorization is actually working?
A: Look for a clear separation between attempted and executed actions.
Practitioner guidance
- Inventory every agent credential Build a complete inventory of tokens, service accounts, and ephemeral credentials used by agents, then record last-rotated dates and owning principals.
- Move authorization into the data path Enforce allow or deny decisions on each request using live context such as identity, resource, action type, and request origin.
- Broker agent credentials with short-lived assertions Replace durable bearer tokens with short-lived scoped assertions signed by an enforcement layer, so backend services never receive raw OAuth tokens or reusable secrets from agents.
Bottom line: Agentic AI invalidates identity assumptions built around a human user sitting behind each request, which makes static scopes and session controls unreliable.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
30/07/2026 10:55 pm
Agentic AI creates an assumption collapse in identity governance: least privilege was designed for actors whose intent is knowable at provisioning time. That assumption fails when the actor decomposes intent at runtime and selects actions dynamically from a tool set. The implication is not simply tighter access control, but a rethink of where privilege is even definable for autonomous systems.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when an agent acts on behalf of a human principal?
A: They should preserve attribution from the initiating person through every hop, tool call, and backend service so the action can be traced end to end. The agent should not become a separate standing identity with its own entitlements. That keeps accountability intact while still allowing the workflow to run under live policy.
👉 Read our full editorial: Identity was built for humans: agentic AI changes the trust model