Notifications
Clear all
Topic starter
14/09/2026 10:09 am
TL;DR: AI agents running through employee accounts blur accountability, over-extend privilege, and break audit trails, according to iProov's analysis of Gartner's 2026 digital identity Hype Cycle. Separate identities, short-lived credentials, and intent-based access control are becoming the baseline for governing agentic access safely.
NHIMG editorial — based on content published by iProov: AI agent identity and the risks of borrowed credentials
By the numbers:
- NHIs outnumber human identities by 25x to 50x in modern enterprises.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures.
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: Why do shared credentials become riskier when AI systems are in the workflow?
A: Shared credentials become riskier because AI systems can act at machine speed across multiple tools and sessions, while human governance still assumes slower, reviewable use.
Q: What are the signs that AI agent permissions are too broad in enterprise environments?
A: Common warning signs include agents accessing tools they do not need, performing irreversible actions without confirmation, retrieving cross-tenant or unrelated data, and acting with long-lived credentials.
Practitioner guidance
- Separate agent identity from employee identity Assign each AI agent its own unique record, named owner, and scoped permissions so actions are not logged under a human user's account.
- Replace standing access with task-scoped credentials Issue short-lived credentials that expire when the task completes, and remove any long-lived password or API key that lets an agent continue acting after the intended work is done.
- Add intent checks before high-impact actions Require the agent's planned action to be evaluated against the user's captured intent for transactions, account changes, or external communications.
What's in the full article
iProov's full article covers the operational detail this post intentionally leaves for the source:
- Gartner-based framing for AI agent identity and the accountability gap in enterprise IAM
- Examples of how borrowed employee credentials distort audit logs and non-repudiation
- Intent-based access control as an emerging authorization pattern for agentic systems
- Practical discussion of separate identity, ownership, and lifecycle handling for agents
👉 Read iProov's analysis of AI agent identity and borrowed credentials →
AI agent identity gaps: what IAM teams need to fix now?
Explore further
14/09/2026 10:10 am
AI agent identity is a distinct governance problem, not a rename of service account management. Service accounts are usually static, workload-bound, and owned by operational teams, while AI agents can decide, sequence, and execute actions at runtime. That difference means the control question changes from 'who owns this credential?' to 'what authority does this actor have to make choices on behalf of a person?' Practitioners should treat agent identity as a new class of governed actor rather than a repackaged machine account.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which means most teams cannot reliably inventory the identities now driving machine and agent access.
A question worth separating out:
Q: Should organisations use ephemeral credentials for AI agents?
A: Yes, but only as part of a broader runtime control model. Ephemeral credentials reduce standing exposure, but they do not solve scoping, logging, or accountability on their own. Organisations should pair short-lived access with task context, tamper-evident logs, and automatic revocation when the agent finishes or changes intent.
👉 Read our full editorial: AI agent identity gaps expose accountability and access risk
