Skip to content

Getting started

This page is the quickest path to understanding AegisAgent: what it is, its components, the architecture, and the use cases it targets.

What AegisAgent is

AegisAgent is the integrity layer for AI agent actions, delivered as an integrity-anchored Agent SOC. It sits at the tool-call boundary — standalone or layered onto a gateway you already run — and guarantees what competitors only decide:

  1. The human-approved action is the action that executes. The exact action is frozen, SHA-256 hashed, and the approval is bound to that hash; the SDK fails closed on any mismatch, replay, or expiry.
  2. Untrusted-origin content cannot drive a privileged action. A deterministic 6-level source-trust label is a first-class policy input.
  3. Every decision is provable. A hash-chained, verifiable receipt is emitted for each action and streamed into a SOC that detects, correlates, contains, and proves.

Components

Component Role
Gateway (Rust + Axum) The runtime: authorizes every action with Cedar, manages approvals, writes receipts, emits SOC events. Binds 127.0.0.1:8080 in dev.
Policy engine (Cedar) Deterministic allow / deny / require_approval decisions; provenance + approval gates live here (policies.cedar).
SDKs In-agent interception. Python (complete reference), Go and TypeScript (canonicalizer verified; client + decorator in progress).
Approval integrity engine Freeze → hash → bind → single-use consume → fail-closed.
Trust-provenance gate The 6 deterministic source-trust levels.
Verifiable receipts Hash-chained, tamper-evident evidence + reference verifier + CLI (aegis-verify-receipts).
MCP Gateway Lite Register / discover / pin MCP tools; manifest-drift detection.
Agent SOC (designed) Async detection, correlation, response, console — consumes the event stream.

Architecture at a glance

AegisAgent runs two planes:

INLINE PLANE (synchronous, <75 ms — the action path)
  Agent SDK ──► Gateway ──► Cedar ──► allow | deny | require_approval
       │ freezes action_hash · binds approval · emits receipt
       ▼ emit Agent Security Event (fire-and-forget)
ASYNC SOC PLANE (out-of-band)
  Event bus ──► detect ──► correlate ──► alert ──► { respond · index · notify · RCA }

The inline plane decides and enforces in real time; the SOC plane monitors and responds out-of-band and never adds latency to the action path. See the Technical design for the full picture and the Agent SOC design for the monitoring plane.

Use cases

  • Guard high-risk agent actions — merge to main, deploy, IAM changes, refunds, customer-data export, prod DB writes — with provably-correct human approval.
  • Defend against indirect prompt injection — deterministically deny mutating actions triggered by untrusted external content (the confused-deputy attack).
  • Prove human oversight — export verifiable receipts for SOC 2 and EU AI Act Article 14.
  • Run a SOC for your agents — detect, correlate, and contain across a whole agent run, with provable incident timelines.
  • Govern an agent fleet — track AI agents as a digital workforce.

Next steps

  1. Install the gateway and run the zero-setup demo.
  2. Connect an agent — choose inline SDK, proxy, or agentless.
  3. Explore the Agent SOC and the Console UI.