AI agents and governance gaps: what IAM teams need to do now

TL;DR: Gartner says only 17% of organisations have deployed AI agents, while 42% expect to do so within 12 months and another 22% within the following year, but the supporting infrastructure for integration, security, governance, and financial management is still maturing. The harder problem is not adoption speed but the fact that access review and credential controls were built for actors whose intent and timing are known before execution begins.

NHIMG editorial — based on content published by 1Password: AI agent governance gaps and the controls enterprises need before deployment

By the numbers:

• Only 17% of organizations have deployed AI agents so far, while 42% expect to do so in the next 12 months, and another 22% within the following year.

Questions worth separating out

Q: How should security teams govern semiautonomous AI agents before they go live?

A: Start with task-scoped permissions, explicit credential lifecycles, and human oversight points before deployment volume makes retrofits impractical.

Q: Why do AI agents complicate traditional IAM and PAM models?

A: Traditional IAM and PAM assume a stable identity whose access can be provisioned, reviewed, and recertified over time.

Q: What do security teams get wrong about auditability for AI agents?

A: Teams often treat auditability as a logging requirement when it is actually the proof that human intent still survives delegation.

Practitioner guidance

• Define task-scoped permissions for each agent Limit every agent to the minimum credential set required for one purpose, and make the issued identity reflect that scope.
• Bind credential validity to agent retirement and compromise state Set explicit issuance, expiry, and revocation conditions so the credential can be withdrawn the moment the agent is retired, reconfigured, or suspected of abuse.
• Record the full human-to-agent authorization chain Log the original human approval, the orchestrating agent, every subagent handoff, and the credential used at each step.

What's in the full article

1Password's full article covers the operational detail this post intentionally leaves for the source:

• The article's breakdown of how enterprise AI assistants, coding agents, and analytics agents create different governance risks.
• The specific 1Password decision points on minimum permissions, credential lifecycle, and human oversight before execution.
• The article's discussion of why pre-authorization is required for irreversible agent actions.
• The section on how authorization fragments across orchestrator and subagent credentials.

👉 Read 1Password's analysis of AI agent governance gaps and control decisions →

AI agents and governance gaps: what IAM teams need to do now?

Explore further

View Full Forum →  |  NHI Foundation Course →