Notifications
Clear all
Topic starter
08/06/2026 5:09 pm
TL;DR: AI agents are turning single-purpose non-human identities into multi-identity access chains that expand permissions, blur ownership, and raise the risk of living-off-the-land abuse, according to Astrix Security's analysis. The governance problem is no longer just credential hygiene, but proving which actor owns which access path when AI behavior becomes nondeterministic.
NHIMG editorial — based on content published by Astrix Security: AI agent identity risk and the rise of multi-NHI access
By the numbers:
- 1:100., ption could drastically increase this ratio, potentially reaching 1:100.
- Organizations currently exhibit a 1:40 human-to-NHI ratio.
Questions worth separating out
Q: How should security teams govern AI agents that rely on multiple non-human identities?
A: Treat the agent and its linked identities as one access graph.
Q: Why do AI agents increase non-human identity risk in enterprises?
A: AI agents increase risk because they often need broader cross-system access than a single workload or script, and they can accumulate several identities to do that work.
Q: What breaks when AI-associated NHIs are treated like ordinary automation?
A: Visibility and accountability break first.
Practitioner guidance
- Inventory every identity attached to each AI agent Map each agent to its OAuth apps, API keys, service accounts, session tokens, and webhooks so the full access chain is visible in one record.
- Separate administrative access from routine agent access Classify any agent that can write, administer, or cross systems as high-risk and subject it to stronger approvals, logging, and review than ordinary automation.
- Tie agent creation to explicit ownership and offboarding Require a named owner, expected usage timeframe, and decommission trigger for every AI-related NHI so the identity can be revoked when the task ends.
What's in the full article
Astrix Security's full article covers the operational detail this post intentionally leaves for the source:
- Category-by-category breakdown of AI systems and the specific NHIs they use across chatbots, RAG, cloud models, and browser agents
- Operational examples of provisioning, visibility, and posture controls for AI-linked NHIs in enterprise environments
- The article's discussion of living-off-the-land attack paths and why they are difficult to distinguish from normal agent behaviour
- Practical recommendations for baselining, monitoring, and automated response around AI-associated identities
👉 Read Astrix Security's analysis of AI agent identity risk and NHI sprawl →
AI agent credentials and NHI sprawl: what IAM teams need now?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
08/06/2026 7:11 pm
AI agents turn NHI governance from a credential problem into an identity-graph problem. The article shows that an agent may depend on many NHIs across SaaS, cloud, email, and database systems, which means security teams can no longer assess exposure by looking at a single secret or token in isolation. The access decision must be made against the full chain of delegated identities, because that is where the real blast radius lives. Practitioners should treat agent access as a composite entitlement structure, not a point credential.
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, with 77% of these incidents resulting in tangible damage.
A question worth separating out:
Q: How can organisations detect living-off-the-land attacks against AI identities?
A: Focus on behavioural anomalies rather than tool signatures alone. Build baselines for normal agent destinations, frequency, and write activity, then alert when an AI-associated NHI starts moving laterally, accessing unusual systems, or producing activity that does not match its declared purpose.
👉 Read our full editorial: AI agents are multiplying NHI sprawl and access risk
