IGA for non-human identities

Governance for AI agents in your ERP.

Your IAM doesn’t see the agents calling your ERPs. Your ERP roles don’t model toxic access combinations across Oracle, Workday, Salesforce, and ServiceNow. AgentGov does — in real time, with evidence you can hand to your auditor.

Providers
4
SoD rules
61
Security layers
3
Pre-flight checkBlocked
AgentGov three-layer security model: WHO, WHAT, WHICHIdentity (WHO) is an AI agent linked to a human principal. Functional (WHAT) duties include Create Invoice and Approve Payment — a toxic combination flagged in red. Data scope (WHICH) restricts the conflict to the EMEA Finance business unit.WHO · IDENTITYAgent · Invoice Botlinked to principal: Jane Doe (Human)WHAT · DUTIESCreate Invoice×Approve PaymentTOXIC COMBINATION · SOD-FIN-001WHICH · DATA SCOPEEMEA Finance · BU 07conflict fires only on same business unitMCP DECISION · DENY · AUDIT LOGGED · 4ms

Built for governance on

Oracle FusionSalesforceWorkdayServiceNow
  • policy61 pre-built SoD rules
  • gavelEU AI Act evidence
  • lockHash-chain audit trail
The governance gap

The two places your existing controls stop.

Governance teams already own IAM and ERP role design. Neither was built for the agents that are now making the calls.

person_off

IAM treats agents as humans.

Your identity platform was designed for people who log in. AI agents operate through service accounts, shared API keys, and machine tokens — invisible to the controls you already own. When an agent does something risky, nobody gets a review.

hub

ERP roles don't see across systems.

Oracle doesn't know what Salesforce granted. Workday doesn't know what the agent can do in ServiceNow. Toxic duty combinations form across providers and under shared identities — and your SoD review never catches them.

How it works

Three steps to governed agents.

Ship in weeks, not quarters. Unmapped actions are denied by default — fail-closed, not fail-open.

  1. 01cloud_sync

    Connect your ERPs.

    One-way sync from Oracle Fusion, Salesforce, Workday, and ServiceNow pulls agents, roles, duties, and data scopes into a unified graph. No changes to your source systems.

  2. 02radar

    Check every action pre-flight.

    Your agent calls the MCP `check_action` tool before sensitive operations. AgentGov resolves the agent's duties, evaluates 61 cross-provider SoD rules, and returns allow, deny, or audit — in milliseconds.

  3. 03receipt_long

    Prove it to the auditor.

    Every decision is committed to a hash-chained audit log. Export evidence packages mapped to EU AI Act articles, run attestation campaigns, and certify agent access on a schedule.

Capabilities

The controls governance teams already know — extended to agents.

Shipped today. No vaporware, no “coming soon” boxes.

group

Cross-identity SoD.

Detects toxic combinations that span an agent and the human principal it acts for. If your invoice bot and Jane Doe collectively hold both sides of a segregation rule, AgentGov catches it.

layers

Data-scope-aware rules.

Conflicts only fire when both sides overlap on a scope dimension (same business unit, legal entity, or ledger). Prevents the false positives that bury real violations.

bolt

MCP pre-flight, fail-closed.

Agents call `check_action` before sensitive operations. Unmapped actions deny by default. OAuth 2.1 bearer tokens with 15-minute TTL; mTLS at the edge in production.

lock

Immutable hash-chain audit.

Every governance decision is committed to a PostgreSQL-trigger-backed hash chain. Tamper-evident by construction. 16 event types covering lifecycle, entitlements, and agent actions.

account_tree

Three-layer security model.

WHO (identity principals), WHAT (duty roles from a hierarchical role DAG), WHICH (data scopes from job role + security profile). The same model compliance teams already speak.

integration_instructions

Drop-in agent adapters.

Ship as a LangChain tool wrapper or a CrewAI decorator — no policy DSL to learn. Existing agents gain governance in a dozen lines; new agents are governed by default.

Integrations

Four ERPs. Sixty-one rules. Zero custom DSL.

Every action you map earns a governed path. Everything unmapped is denied.

Oracle Fusion

Finance · SCM · HCM

16

SoD rules

  • priority_highCreate Supplier × Pay Invoice
  • priority_highPost Journal × Approve Journal
  • priority_highMaintain Bank Account × Disburse Funds

Salesforce

Object · System perms

15

SoD rules

  • priority_highModify All Data × Manage Users
  • priority_highExport Reports × View Encrypted Data
  • priority_highCustomize Application × Manage Profiles

Workday

HCM · Payroll · Finance

15

SoD rules

  • priority_highHire Employee × Approve Compensation
  • priority_highProcess Payroll × Approve Pay Run
  • priority_highEnter Supplier Invoice × Approve Payment

ServiceNow

ITSM · Security · HR

15

SoD rules

  • priority_highGrant Admin Role × Remove Audit Log
  • priority_highRaise Change × Approve CAB
  • priority_highCreate User × Assign ITIL Role

Fail-closed by design: actions not mapped to a duty are denied at the MCP server.

For agent builders

Drop-in governance. No policy DSL.

Wrap one tool with check_actionand every call gets resolved against your org’s role DAG, SoD rules, and data scopes. Adapters ship for LangChain and CrewAI.

  • checkOAuth 2.1 client_credentials with 15-minute bearer tokens
  • checkmTLS edge in production (internal CA)
  • checkDecision + reason + violations + audit_id in every response
  • checkUnmapped actions deny by default — fail-closed

agents/invoice_bot.py

from agentgov import AgentGovClientfrom langchain.tools import tool client = AgentGovClient("https://mcp.your-company.com") @tooldef approve_payment(invoice_id: str, amount: float):    decision = client.check_action(        agent_id="invoice-bot-42",        action="oracle.finance.payment.approve",        context={"amount": amount, "business_unit": "EMEA_FIN"},    )    if decision.decision == "deny":        raise PermissionError(decision.reason)    # proceed with the approval
ResponseBlocked

decision.json

{  "decision": "deny",  "reason": "SoD conflict: agent already holds CreateInvoice duty",  "violations": [{    "rule_id": "SOD-FIN-001",    "rule_scope": "cross_identity",    "data_scope_overlap": true  }],  "audit_id": "01JN7H...K3Y2",  "latency_ms": 4}
EU AI Act alignment

Evidence you can hand to the auditor.

AgentGov’s hash-chain audit log, SoD detector runs, and attestation campaigns generate the artefacts required by the EU AI Act high-risk system obligations. Export per framework, download per article.

  • Art. 9

    Risk management

  • Art. 10

    Data governance

  • Art. 12

    Recordkeeping

  • Art. 13

    Transparency

  • Art. 14

    Human oversight

  • Art. 17

    Quality management

Ship governed agents

Governed AI agents in your ERP this quarter.

30-minute demo. Walk through a live SoD violation across Oracle and Workday, then see the audit evidence exported to an EU AI Act package.