Everyone is deploying AI agents. Almost nobody is giving them badges.

Two numbers capture the state of enterprise AI in 2026, at least as the identity industry tells it. In its e-book The AI Agent Era, Okta reports that 91% of organizations are already using AI agents in production, while only 10% have a well-developed strategy for managing non-human identities. Okta does not describe the sample or survey behind those figures, so read them as directional, not universal.

Even discounted for vendor optimism, the gap is the story of 2026. AI agents are reaching production faster than the identity programs meant to govern them, and on Okta's numbers only one in ten organizations has a well-developed strategy for the identities those agents use.

We spent two decades building identity programs for people: badges, single sign-on, multi-factor authentication, offboarding checklists. AI agents arrived faster than that machinery could adapt. What is left is a workforce most companies are not set up to count, attribute, or offboard.

The workforce you cannot see

Non-human identities are not new. Service accounts, API keys, OAuth tokens and bots have been multiplying for years. Research cited in a 2026 Cloud Security Alliance paper puts the ratio at 45 non-human identities for every human one across the average enterprise, and 144 to 1 in cloud-native environments, up from 92 to 1 in the first half of 2024. One published audit of a Fortune 500 financial institution found 4.2 million non-human identities against roughly 50,000 human user accounts.

AI agents turn a hygiene problem into an authority problem. A service account runs the same job every night. An agent decides which job to run. It reads email, queries the warehouse, calls vendor APIs and chains those steps together at machine speed. Every one of those actions rides on a credential someone issued and nobody reviewed.

The governance vacuum

The CSA paper, The Non-Human Identity Governance Vacuum, assembles findings from several industry surveys and reports, each with its own sample. The direction across them is consistent:

• 78% of organizations have no documented policy for creating or removing AI identities.
• More than 16% do not track the creation of AI-related identities at all.
• 51% report no clear ownership for AI identities.
• Only 20% have formal API key rotation procedures, and 24% take more than 24 hours to rotate or revoke a credential they already know is exposed.

The cost shows up in breach data. IBM's 2025 Cost of a Data Breach report, cited in the same paper, found that 97% of organizations that suffered an AI-related breach lacked proper AI access controls. Shadow AI, where employees point unapproved tools at company data, played a role in 20% of breaches and added roughly $670,000 to the average bill.

This is not a tooling gap you can buy your way out of. It is an ownership gap. Identities nobody owns do not get rotated, scoped, reviewed or revoked.

The standards are catching up

Two 2026 efforts are worth reading in full.

In February, NIST's National Cybersecurity Center of Excellence published a draft concept paper on applying existing identity standards to software and AI agents. The premise is blunt: the standards for identification, authentication and authorization already exist. The work now is demonstrating how they apply to agentic architectures, not inventing new ones.

In March, the Coalition for Secure AI published version 1.0 of its Agentic Identity and Access Management guidance. Its imperatives read like a job description for the next three years of IAM work: treat agents as first-class identities with their own lifecycle, eliminate standing privilege in favor of short-lived, task-scoped credentials, keep an agent's baseline permissions distinct from the rights of the human it acts for, and be able to prove control on demand, meaning you can reconstruct which agents existed and what they did.

Okta frames the same shift from the vendor side: identity is becoming the control plane for autonomous systems, because it is the one layer that sees every action an agent takes.

What I would do Monday morning

This section is my opinion, built from the sources above.

1. Count your agents before you govern them. You cannot secure identities you have never inventoried, and 16% of organizations are not even tracking new ones as they appear.
2. Give every agent a named owner. Not a team. A person who answers for what it does and confirms it still needs to exist.
3. Issue credentials like concert tickets, not apartment keys. Short-lived, scoped to the task, expired when the task ends.
4. Separate what the agent may do from what the human behind it may do. Delegation is where intent gets lost.
5. Practice firing one. Pick an agent, revoke its credentials, and time the drill. In the surveys CSA cites, roughly a quarter of organizations need more than a day to rotate or revoke an exposed credential. That is too long.

Limits of this analysis

The numbers here come from vendor-published research and industry surveys with different methodologies and populations, and some, like Okta's, do not describe their sample at all. Treat any single figure as directional. What I trust is the pattern: across four independent sources, identity governance is lagging agent deployment by a wide margin. This is analysis, not legal or security advice.

Sources

• Okta, The AI Agent Era: Rethinking Identity, Trust, and Control (2026): https://www.okta.com/sites/default/files/2026-02/The-AI-agent-era.pdf
• Cloud Security Alliance, The Non-Human Identity Governance Vacuum (May 2026): https://labs.cloudsecurityalliance.org/wp-content/uploads/2026/05/CSA_whitepaper_nonhuman_identity_agentic_ai_governance_v1-csa-styled.pdf
• Coalition for Secure AI, Agentic Identity and Access Management v1.0 (March 2026): https://www.coalitionforsecureai.org/wp-content/uploads/2026/04/agentic-identity-and-access-control.pdf
• NIST NCCoE, Accelerating the Adoption of Software and AI Agent Identity and Authorization, draft concept paper (February 2026): https://www.nccoe.nist.gov/sites/default/files/2026-02/accelerating-the-adoption-of-software-and-ai-agent-identity-and-authorization-concept-paper.pdf