Tools · Agent identity & NHI
AI agent identity and non-human identity (NHI) tools
These products manage AI agents as identities: each agent, like other non-human identities (NHI) such as service accounts and API keys, is tied to a named human owner and scoped permissions, and several of the products replace stored keys with short-lived credentials. Many also find the agents and keys already in use and record which agent acted for which person. A team needs one when agents reach company systems through shared service accounts or long-lived keys, because then no log can say which agent did what, and no single agent can be cut off without breaking the others.
Agent identity & NHI 14
-
Aembit IAM for Agentic AI (vendor site, opens in a new tab)
generally availableAembit
Controls when AI agents can reach MCP servers and the systems behind them, using a combined identity of the agent and the person it acts for. Agents never hold the downstream credentials: Aembit exchanges tokens per request, logs every access attempt and can revoke access at once.
-
Amazon Bedrock AgentCore Identity (vendor site, opens in a new tab)
generally availableIdentity and credential service for AI agents built on AgentCore. Agent identities are workload identities that let agents reach AWS resources and third-party services for a user or on their own, with authentication, authorization and audit trails.
-
Astrix (vendor site, opens in a new tab)
generally availableAstrix Security
Keeps an inventory of AI agents, MCP servers and non-human identities and flags excess privilege, risky configuration and abnormal activity. Its Agent Control Plane provisions new agents with short-lived, just-in-time, scoped credentials, and threat detection covers compromised credentials and out-of-scope agent actions.
-
Auth0 for AI Agents (vendor site, opens in a new tab)
generally availableDeveloper identity service for agents that act for users: it authenticates the user, stores the tokens agents use to call services such as Google Drive, Jira and Slack, asks the user to confirm critical actions, and limits which documents an agent can retrieve in RAG.
-
Cyera Identity (vendor site, opens in a new tab)
generally availableInventories service accounts, API keys, tokens and AI agents across cloud, SaaS, on-premises and AI platforms, including unapproved MCP servers, and ties each to an owner and the data it can reach. Agent requests are checked against access policy in real time and granted short-lived, task-scoped identities, with each session recorded and stoppable.
-
Keycard (vendor site, opens in a new tab)
generally availableKeycard
Gives each agent its own identity and issues short-lived, task-scoped credentials only after confirming the workload and the person it acts for and evaluating policy written in Cedar. Denied requests get no credential, every decision is logged for export to a SIEM, and a revoked credential stops working wherever it applies.
-
Microsoft Entra Agent ID (vendor site, opens in a new tab)
generally availableGives AI agents their own identities in Microsoft Entra ID, with identity, lifecycle and access controls applied as they are for employees, and monitoring of agent activity. Agent identities are available to all Entra customers; applying Entra security controls to agents requires Microsoft Agent 365, which is included in Microsoft 365 E7.
-
Okta for AI Agents (vendor site, opens in a new tab)
generally availableRegisters AI agents as identities with named human owners, enforces least-privilege policy on each agent connection, and runs access certification campaigns on agent permissions. Agent SSO gives agents that support Cross App Access short-lived tokens in place of stored credentials, and deactivating an agent blocks its new sessions.
-
Permiso AI Security (vendor site, opens in a new tab)
generally availableDiscovers AI agents in cloud functions, containers, VMs and code repositories, keeps a registry of them, and attributes agent runs, events and tool calls to the human, machine or AI identity behind them across cloud, SaaS and on-premises systems. It detects threats in that activity and can stop an agent with a kill switch.
-
Rig Security (vendor site, opens in a new tab)
generally availableRig Security on the vendor map
Resolves accounts, tokens and AI agents to the person behind each one and maps which grants chain into paths to production data. It removes access nobody needs, joins identity alerts into a single attack timeline, and on laptops, servers and clusters can block a risky agent action without blocking the person whose session the agent uses.
-
Rippling Agent Identity Management (vendor site, opens in a new tab)
generally availableKeeps AI agents as records in Rippling alongside employees and service accounts, as one of the products in Rippling AI Governance. Admins give each agent an owner and permissions and provision it into third-party apps with the access controls they already use in Rippling. An agent works either on permissions an employee delegates or under its own managed identity; in both cases admins can see its access, spend and activity, and can revoke it from the same system.
-
SailPoint Agentic Fabric (vendor site, opens in a new tab)
generally availableDiscovers AI agents and machine identities along with the credentials, APIs and tokens they use, and maps each agent to its human owner, permissions, sessions and data. Governance teams review and revoke agent access, and behavior is monitored for threats.
-
Token Security (vendor site, opens in a new tab)
generally availableToken Security
Discovers AI agents and MCP servers across cloud, SaaS and internal tools along with the non-human identities and tokens they use. It assigns owners, right-sizes agent access and traces actions across chains of agents.
-
Zuma (vendor site, opens in a new tab)
generally availableDiscovers AI agents, tools, MCP servers and non-human identities and keeps them in one registry with owners and risk insights. It authorizes what agents can touch in apps and data at runtime and governs each agent from registration to retirement, including offboarding orphaned or inactive ones.
Recent launches
- Microsoft Dynamic Permissions and Dynamic Conditional Access for agents · announced
- ServiceNow AI Passport · announced
- Descope Agentic Identity Hub 3.0 · announced
- Kong Token Vault · generally available
- CrowdStrike Agentic Identity Provider · announced
- Okta Agent SSO · generally available
- Agent Identity auth manager (Google) · generally available
- Rippling Agent Identity Management · generally available
- SailPoint Agentic Fabric · generally available
Announced in the last 90 days. Each launch on New tools links the vendor's own announcement.
The briefing
New AI agent governance tools, by email
The briefing's New Tools section covers the latest governance launches, each linked to the vendor's announcement, next to the news that decides which ones matter. At least once a week, five-minute read, free.
You confirm by email. Unsubscribe in one click.
Questions to ask vendors
Neutral questions for a request for proposal (RFP) or a security questionnaire. No product here is named as the answer.
-
Does each agent get its own identity and credential, or do agents share service accounts under the hood?
-
Are credentials short-lived and automatically rotated, or static keys that live until someone remembers them?
-
Is every identity assigned a human owner, and is that ownership recorded somewhere we can query?
-
When an agent acts for a user, does the log capture both the agent and the user it acted on behalf of?
-
How fast can we revoke one agent's access without touching any other agent?
-
When an agent acts on behalf of a user, is its effective access the intersection of its own permissions and that user's?
If the agent's access is broader than the user's, injected content can use the agent's authority to do what the user never could. This is the confused deputy problem.
More questions, grouped by topic: Questions to ask AI agent security vendors.
Related incidents
- CERT-In said AI agents under evaluation read personal and confidential records at Indian organizations
- A breach at OpenCode may have exposed the AI provider keys users stored in OpenCode Console
- Infostealer malware hijacked Claude accounts through stolen session tokens
- Attackers stole a METR API key and burned about $600,000 in AI credits
Every record in the AI agent incident database links the sources that reported it.
Missing a product, or found an entry that is out of date? Write to [email protected]. A submission is read, never paid for, and does not guarantee a listing. The glossary defines the terms used here.