Skip to main content
Oathera logo Oathera
Use casesFive stories: no identity, a new identity, impersonation, cloning, and a call outside the boundary. PlatformOathera Agent Enrollment, the Oathera Identity Service and Oathera Agent Enforcement. FeaturesWhat Oathera does for you, grouped by purpose. IntegrationsYour identity provider, your MCP servers, your cloud. SecurityHow Oathera fails closed, and what it doesn't do.
Developer sectionComponents, the identity token, standards and settings. Data sheetsThe buyer and developer data sheets, as PDFs. LearnGuides on giving AI agents an identity of their own. GlossaryPrincipal, sponsor, anchor key, key digest, identity token. SimulatorWatch a stolen token, a replayed proof and a tampered call get refused.
About usThe team and the mission behind Oathera. BlogPosts from the Oathera team. CareersOpen roles at Oathera. ContactTalk to the founders, or become a design partner. LinkedIn ↗Oathera on LinkedIn.
Privacy PolicyHow we handle data. Terms of ServiceTerms for using Oathera. Data Processing AgreementOur DPA for customers. Sub-processorsThird parties we rely on.
Become a design partner

Learn · Governance

Non-human identity (NHI) governance for AI agents

Non-human identity (NHI) is the family of identities that are not people: service accounts, API keys, tokens, certificates and now AI agents. NHI governance is how you inventory, approve, monitor and retire them. For autonomous agents, governance has to add a named accountable person and a check on every action.

On this page

  1. Same family, different names
  2. NHI lifecycle management for agents
  3. OWASP NHI questions
  4. How Oathera helps
  5. FAQ

Same family, different names

Non-human identity (NHI) is the common term in security programmes. Non-person entity (NPE) is the term used in US federal and defence settings. Machine identity usually means certificates and keys for devices and workloads. Workload identity means an identity for running software. An AI agent is a non-human identity that also makes decisions, so it needs more than a key.

NHI lifecycle management for agents

  1. Discover. Find agents that call your tools with no identity.
  2. Enroll and approve. Give each agent its own identity and have a named person approve it.
  3. Check. Compare the host at every token request and verify a proof on every call.
  4. Review. Record what each agent did and who answered for it.
  5. Retire. Revoke the agent, or stop every agent a departing person approved.

OWASP NHI questions

OWASP publishes a Non-Human Identity Top 10. When an agent answers the OWASP NHI questionnaire at enrollment, the Oathera Identity Service derives a risk tier from 1 to 4 and records NHI1 to NHI10 findings. The answers are self-reported, not independently proofed.

How Oathera helps

Oathera treats the agent as a governed non-human identity: its key is created on its own host, a principal approves it, its risk tier is recorded and every call is checked. Oathera Agent Enforcement lists discovered agents, and revocation takes effect at the agent's next token request and next boundary decision.

Oathera does not verify people, judge model output, inspect or rewrite prompts, or replace your identity provider. Your identity provider and proofing sources do the first; Oathera is the layer under them for agents.

FAQ

What is NHI governance?

The practice of inventorying, approving, monitoring and retiring non-human identities such as service accounts, keys, certificates and AI agents.

What is a non-person entity (NPE)?

A term used in US federal and defence contexts for identities that are not people. It maps to non-human identity.

How is an AI agent different from a service account?

A service account is a credential. An agent decides what to do. So an agent needs an accountable person and a check on each action, not only a secret.

What is NHI lifecycle management?

Managing a non-human identity from discovery and approval through monitoring to revocation.

Related: What agentic identity governance looks like · Per-agent identity vs shared API keys · Shadow AI agent discovery and enrollment

Become a design partner Watch the simulator More guides

← Back to Learn
Oathera logo Oathera

Every AI agent, sworn in. Oathera gives every AI agent an identity bound to the machine it runs on, with a named person who answers for it, and checked every time it acts.

Product

  • Use cases
  • Platform
  • Features
  • Integrations
  • Security

Developers

  • Developer section
  • Data sheets
  • Learn
  • Glossary
  • Simulator

Company

  • About us
  • Blog
  • Careers
  • Contact
  • GitHub

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Sub-processors
© 2026 Oathera Inc. · All rights reserved
Know Your Agent (KYA)

Cookie preferences

We use cookies to run this site and, with your consent, to understand usage and improve Oathera. Strictly necessary cookies are always on; you can choose whether to allow analytics and marketing cookies below.

Read the privacy policy

  • Strictly necessaryAlways on

    Required for the site to work, security, load balancing, and remembering your cookie choices. These cannot be switched off.

  • Help us measure traffic and see how the site is used, so we can improve it. No personal profiles are built.

  • Used to make messages about Oathera more relevant across other sites. Off unless you turn it on.