DOCS

How It Works

Delegation chain of custody, assurance evidence and the SURADAR layers.

One product, two halves

SURADAR provides assurance for AI agents: a verifiable chain of custody for the authority an agent acts on.

Delegation chain of custody is the assurance half. SURADAR records each grant of authority from person to agent or agent to agent as a signed grant. It verifies the chain before a tool call is allowed. Decisions and grants go to a verification-guarded, append-only log. A reviewer can verify an exported evidence bundle offline with the evidence-verify tool and a pinned public key, without network calls. A divergence detector compares the authority an agent was granted with what it does and flags differences.

L1 through L5 form the substrate. L6 Memory Provenance adds signed, verification-guarded provenance for agent memory writes and reads.

The layers

L1 Core Auth

Every request is signed and verified individually, with replay prevention. There is no implicit trust between requests.

L2 Identity

This layer provides federation with OpenID Connect (OIDC) providers, Secure Production Identity Framework for Everyone (SPIFFE) and cloud workload identity. It also provides enrollment and consent.

L3 Transaction Binding

This layer binds a high-stakes action to the verified agent identity.

L4 Agent Registry

Agent records contain a description, owner, capabilities and scopes.

L5 Governance

This layer provides policy evaluation, risk analysis and security information and event management (SIEM) event export. It evaluates Cedar policies loaded from local files. A forbid rule always wins over a permit rule. Policy versions must be activated explicitly before they take effect.

What happens on a tool call

suradar-pdp follows this authorization flow:

  1. Authenticate the caller.
  2. Verify the delegation chain.
  3. Check scopes, expiry and replay.
  4. Evaluate policy.
  5. Return allow or deny.
  6. Write one decision-log line per authorize response.

How it fits into your stack

An integrator protects a service by wrapping its Hypertext Transfer Protocol (HTTP) handlers with the SURADAR middleware stack in the Go library, or by putting suradar-pdp in front of tool calls. Agents sign requests with a software development kit (SDK).

SURADAR works with OAuth 2.1, Model Context Protocol (MCP), SPIFFE and identity providers such as Okta. It adds a chain of custody on top of these primitives.