TL;DR: AI agents dominated Gartner IAM Summit discussions because they are exposing familiar NHI weaknesses, including visibility gaps, secrets sprawl, hard-coded keys, and immature business mapping, according to Astrix Security. The real issue is that existing IAM programmes still struggle to govern non-human access at the speed and scale agentic adoption demands.
NHIMG editorial — based on content published by Astrix Security: AI agents and identity governance at Gartner IAM Summit
Questions worth separating out
Q: How should security teams govern AI agents alongside existing non-human identities?
A: Treat AI agents as an extension of NHI governance, not as a separate exception.
Q: Why do AI agents expose weaknesses in service account governance?
A: AI agents expose service account weaknesses because they increase access volume, shorten decision cycles, and rely on credentials that often persist longer than the task.
Q: What breaks when identity programmes cannot map access back to a real subject?
A: Governance breaks because access reviews, incident response, and least-privilege decisions all depend on knowing who or what actually holds the entitlement.
Practitioner guidance
- Map non-human identities to business services Build a service-level inventory that links accounts, entitlements, and activity to the business function they support.
- Reduce the lifetime of agent-adjacent secrets Classify secrets used by agents, service accounts, and integrations by exposure impact, then shorten their usable lifetime wherever operationally possible.
- Review non-human access before production scaling Require explicit governance checks before moving AI agents from test to production, including entitlement ownership, least-privilege scope, and revocation paths.
What's in the full article
Astrix Security's full article covers the operational detail this post intentionally leaves for the source:
- The summit-specific practitioner observations that explain how identity teams are talking about AI agents in production planning.
- The full discussion of PQC concerns and why cryptography was framed as a core dependency of identity.
- The source article’s narrative examples and executive-session observations that were condensed here into governance analysis.
- The broader context around how enterprise identity leaders are translating summit themes into programme priorities.
👉 Read Astrix Security's analysis of AI agents and identity governance at Gartner IAM Summit →
AI agents at Gartner IAM Summit: what identity teams should recheck?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
AI agents are not introducing a new identity problem, they are compressing an old one. Service accounts, secrets, and hard-coded credentials were already the weak points in NHI governance. What changes is the operational tempo, because agents force those weaknesses to surface at production speed and scale. The implication is that IAM teams need to judge non-human control maturity by execution speed, not by policy intent.
A few things that frame the scale:
- 88.5% of organisations acknowledge that their non-human IAM practices lag behind or are merely on par with their human identity and access management efforts, according to The 2024 Non-Human Identity Security Report.
- 23.7% of organisations share secrets through insecure methods such as email or messaging applications, which shows how basic NHI hygiene still breaks down in practice.
A question worth separating out:
Q: Should organisations delay AI agent production use until NHI controls improve?
A: Yes, if the current programme still struggles with secrets, entitlement ownership, or business mapping. AI agent deployment amplifies those gaps rather than hiding them. Organisations should move agents into production only after they can show clear ownership, short-lived credentials where possible, and a working revocation path for non-human access.
👉 Read our full editorial: AI agents are resurfacing old identity gaps at Gartner IAM Summit