Why AI agents break the existing NHI model
A traditional service account has a well-defined behaviour envelope. You know what it talks to, because a human engineer wrote the integration. You can describe its authorised scope in a sentence. It is deterministic.
An AI agent is a different animal. It:
- Selects tools at runtime from a set exposed via MCP (Model Context Protocol), A2A (Agent-to-Agent protocol), or similar. A human engineer did not pre-wire which tool is called in which order.
- Is prompted by other agents or by chains of inputs, some of which may be adversarial (prompt injection). The identity authenticating the request and the intent behind the request are increasingly decoupled.
- Operates across identity boundaries on behalf of users, on behalf of tenants, and on behalf of itself, sometimes simultaneously.
- Is often overprivileged by default because the scope needed for a generic assistant to be useful is broad, and because scoping agent capabilities narrowly is hard UX.
The governance model has to evolve. Articles in this hub work through what that looks like in practice.
What is AI agent identity?
Agent identity defined, its relationship to user identity and service identity, and the reference architecture for issuing and verifying it.
Read → ProtocolMCP security
Model Context Protocol, the emerging standard for exposing tools to agents, and the NHI implications of every server, client, and tool call it enables.
Read → AuthenticationAI agent authentication
How agents authenticate to tools and downstream services: OAuth 2.1, OBO (on-behalf-of) flows, workload identity, and the patterns that work at scale.
Read → GovernanceAgentic AI identity governance
Lifecycle, scope, audit, and kill-switch patterns for governing agents at the enterprise scale, and how regulators are framing it.
Read →Where the regulatory frontier sits
The EU AI Act (Regulation 2024/1689) is the first major legal framework that directly regulates the behaviour of agentic systems deployed in the EU. High-risk systems, a category that captures many enterprise agent deployments, must satisfy risk management, data governance, technical documentation, human oversight, and accuracy/robustness requirements. General-purpose AI models (and GPAI models with systemic risk) have their own obligation set, with compliance deadlines through 2026 to 2027. For the identity community, the practical implication is: every agent deployed in a regulated industry will need identity, scope, and audit trail that satisfies regulators. The lightweight implementations shipped by 2024's experimental frameworks will not.
See EU AI Act, NHI implications for the mapping.
Breach context
No breach of major public significance has yet been attributed solely to an AI agent's actions. But the Salesloft Drift breach of 2025 (which involved an AI-powered SaaS integration) is the closest we have to a real-world study of how an AI-adjacent NHI can be leveraged at scale. As agents proliferate and their scopes expand, the breach ledger will grow.
Deep dives
Delegation chains
The record connecting a human decision to the action software took. The evidence most deployments cannot produce.
Agent registries
What a registry must record, why discovery is harder than storage, and how to find agents nobody registered.
Agent revocation and kill paths
Why expiry is not revocation, the four layers of a kill path, and how to measure your real revocation time.
Prompt injection as an identity problem
Authority escalation, not content filtering. The identity-layer controls that bound the damage.
Multi-agent authorization and A2A
What A2A covers and what it does not, and the scope rule that bounds an agent tree by the original consent.
The AI agent lifecycle
Six stages, access reviews with no manager, and why retirement never fires unless you build the trigger.
Human-in-the-loop patterns
Four oversight patterns, and why refusals are the only evidence that oversight is real.
Classifying agent risk
Reach, reversibility and autonomy. Verifiable from your own configuration, unlike model capability.
Incident response for AI agents
Six containment actions in order, and why network isolation is not containment for agents.
Governing MCP servers
Inventory, a three-tier approval model, and the locally installed servers carrying the most access.
Agent credentials in CI/CD
Why pipelines concentrate credentials, and the workload identity model that removes standing secrets.
Agent identity standards
Every active effort mapped with its real status, and what to build now.
Assess your own NHI programme.
Run the free maturity assessment or the OWASP NHI Top 10 self-audit, get your score in the browser, and unlock the full written report.