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

What agentic identity governance looks like

Your security team asks the hard question: when an AI agent takes a destructive action, who is accountable? Agentic identity governance is the set of controls that make the answer provable rather than a shrug. It covers which agent is which, who sponsors it, what it is allowed to do, and how every action is attributed.

On this page

  1. Why agents break traditional IAM
  2. The four pillars
  3. Answering "who is accountable?"
  4. How to implement it
  5. FAQ

Why agents break traditional IAM

Identity and access management grew up around two kinds of actor: human employees and standing service accounts. AI agents are neither. They are created and destroyed constantly, they act with a degree of autonomy, and they frequently operate on behalf of a specific person. Pointing a static service account at many agents collapses them into one indistinguishable actor, which is the opposite of governance. Agentic identity governance exists to restore the which-agent, the what, and the under-whose-authority for software that behaves this way.

The four pillars

  • Identity. Each agent is uniquely and verifiably identifiable. Not a label it asserts about itself, but a cryptographic identity, its anchor key's key digest, it can prove on every request.
  • Sponsorship. Each agent is approved by a named person, and the approval is on record. With Oathera, that person is the principal who signs in through your identity provider and approves the enrollment, and a separate, verified sponsor is recorded for each agent.
  • Authority. Each agent is scoped to least privilege, the specific operations, resources, and audiences it needs, its operational boundary, and that scope is enforced on every request, not just checked once at setup.
  • Attribution and expiry. Every action is provably tied to the agent that took it, in a record you can hand to an auditor, and the agent's identity token expires on its own so authority never quietly outlives its purpose.

Governance is only real if the four pillars are enforced, not documented. A policy that says "agents must have a sponsor" means nothing unless an agent with no sponsor literally cannot act.

Answering "who is accountable?"

When an agent does something destructive, a governed system lets you reconstruct the full chain: this request came from Agent A (proven by its operation proof), Agent A was approved by this named person (recorded at enrollment), Agent A was granted this authority, and the action fell inside or outside that authority. Accountability is no longer a debate, it is a query. Equally important, the blast radius was bounded in advance, because least privilege meant the agent could never have reached beyond its approved scope in the first place.

With Oathera, the first two links are recorded: the operation proof, and the principal on the enrollment record. Each enforced call also gets a signed boundary decision, which checks that the agent and the principal are still active and checks the call against the agent's list of permitted services.

How to implement it

  1. Issue per-agent identity. Replace shared keys with an anchor key and an identity token per agent. See per-agent identity vs shared API keys.
  2. Require an approval at enrollment. Nothing activates until a principal approves the enrollment. See making a named person accountable.
  3. Scope authority to least privilege. Define each agent's operational boundary and enforce it at Oathera Agent Enforcement. See least privilege for agents.
  4. Attribute. Record every boundary decision against the verified identity, and keep the records in your own store: Oathera's audit chain is held in memory, and it is exported to your SIEM or a write-once store. See auditing agent actions.
  5. Expire by default and revoke on demand. Short identity-token lifetimes plus immediate revocation mean authority is never permanent.

Oathera delivers per-agent identity, enrollment approval by a named principal, a boundary decision on every enforced call, and short identity tokens. It records a named sponsor for each agent and checks each agent's list of permitted services. Explore the platform or see every feature.

FAQ

Who is accountable when an AI agent takes a destructive action?

The named person who approved the agent. Agentic identity governance records that approval, scopes what the agent may do, and attributes every action to the agent's verifiable identity, so accountability is provable rather than argued. With Oathera, the principal who approved the agent is on its enrollment record, and a separate, verified sponsor is recorded.

What are the pillars of agentic identity governance?

Identity (each agent is verifiably identifiable), sponsorship (each maps to an accountable sponsor), authority (each is scoped to least privilege and enforced per request), and attribution with expiry (actions are provably attributed and the identity token lapses on its own).

Can I bolt governance onto agents I already run?

Yes. Oathera Agent Enrollment on your MCP server enrolls existing agents, enrollment approvals happen through your own IdP, and enforcement happens at Oathera Agent Enforcement in front of your resource servers, so you add governance without rewriting the agents or the systems they call. The agent signs each call on its own machine, and Oathera Agent Enforcement verifies proofs for any tool you configure.

See the use cases 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.