Agentic Trust Fabric
The security overlay for the agentic ecosystem. Secure agents, tools, and agent-to-agent interactions with Provenance Identity Continuity (PIC) and the Permguard Trust Plane.
- PIC
- Trust Plane
- MCP/A2A
- Agent Security
Permguard provides traditional application authorization through Policy Decision Points, together with a security overlay for the agentic era.
Permguard Admin Preview
The desktop app for the people who run Permguard. Connect your control planes and manage them from one window: the server that hosts them, the ledgers and policies they serve, the events and decisions they record.
Products / 03
Trust, authorization, and isolated execution—one system for governing agents, applications, and services.
The security overlay for the agentic ecosystem. Secure agents, tools, and agent-to-agent interactions with Provenance Identity Continuity (PIC) and the Permguard Trust Plane.
Authorization for services and applications. A Policy Decision Point designed for enterprise applications and built for Zero Trust, resilience, full auditability, and distributed systems.
AI agents, sandboxed. Every agent invocation runs in a fresh, isolated Soglia execution. Its actions cross Soglia guardrails before they can reach the outside world, and the execution is destroyed when it ends.
Policies / Cedar · Rego · Dogwood
A ledger keeps its policies in partitions, each in its own language: Cedar for who may do what, Rego for the rules of an API, Dogwood when the answer depends on what happened before. These are real policies of the Atlas Commerce playground.
// Customer-support staff can inspect orders only inside their merchant.@alias("merchant-support-readers")permit (principal in Role::"support-agents",action == Action::"view",resource) when {principal.merchant == resource.merchant};
Command line / permguard
Create a ledger, plan and apply policies, read the signed objects behind them, ask for a decision: the same CLI, one workflow.
$
$
$
SDKs / your application
With the official SDKs, authorization leaves your code: no more roles and rules hard-wired in every service, one call asks Permguard for the decision. Drag the handle to see the difference.
Decision logs / evidence
Every answer becomes a record, chained to the one before and shipped in signed batches. Read it from your own offset, with the CLI or the API, as many readers as you need: your SIEM, your threat detection, your data lake. Identities stay pseudonymised unless you name what to keep in clear.
Decision log
commerce/order-platform
one writer · signed batches
Your consumer · example
a collector, a stream processor, your own service
GET …/records?from=the decision log API, HTTP or gRPC, from its own offsetproof=truechain and signatures, against the data plane's keysyour schemaone event per decision, as your SIEM expects itby outcomeevery decision to the SIEM and the lake, denials to threat detection tooits own offset · seq 1851
The same consumer, with the CLI · route-decisions.sh
permguard decisions tail --zone commerce --ledger order-platform \--follow --verify --keys data-plane-keys.json -o json \| jq -c '.decisions[] | {time: .at, user: .subject, action, resource, outcome}' \| while read -r event; docurl -s -X POST "$SIEM_URL" -d "$event"case "$(jq -r .outcome <<< "$event")" indeny|deny_by_default) curl -s -X POST "$THREAT_URL" -d "$event" ;;esacecho "$event" >> "lake/$(date +%F).jsonl"done
Routed
1842 permit → SIEM · data lake
1843 permit → SIEM · data lake
1844 deny → SIEM · threat detection · data lake
1845 permit → SIEM · data lake
1846 permit → SIEM · data lake
1847 deny → SIEM · threat detection · data lake
1848 permit → SIEM · data lake
1849 permit → SIEM · data lake
1850 permit → SIEM · data lake
1851 deny → SIEM · threat detection · data lake
Learn / Watch
Explore practical training videos about Permguard, AI agents, authorization, and secure autonomous systems. Available in English, Italian, and Spanish.
Philosophy
Permguard is built on the principles of Provenance Identity Continuity (PIC): formal model first. A mechanism enters Permguard only when the property it enforces can be stated and proved. Whatever cannot be proved stays out, however convenient it would be.
“Authority Continuity for Verifiable Lineage in Distributed Systems and AI Agents” — to be presented at the 24th IEEE International Symposium on Network Computing and Applications, November 10–13, 2026, Syracuse, Italy.
PoP view · Possession
PoP proves control of the token. It cannot see which execution is using it or where that use sits in causal time.
PIC view · Continuity
PIC adds lineage. The same operation, resource, and token become two distinguishable executions.
Model-level results, under the assumptions stated in the paper.
Explore PIC ProtocolTheorem 6 · Exclusion
Authority only narrows along a lineage, never expands. A privilege absent at the origin cannot appear at any later hop, so a request can no longer borrow a deputy's own authority: the confused deputy is not a state a valid PIC execution can represent.
(o, r) ∉ C0 ⟹ (o, r) ∉ CnTheorems 3 – 4 · Lineage
Same principal, same token, same privilege, different lineage: spatially valid, temporally invalid. Possession-only authorization provably cannot tell the two apart, and any policy that does must read the lineage. PIC puts it in the decision.
e = (o, r, ℓ) ∈ O × R × LPlatform / Governance
One governance model between the Agentic Trust Fabric and the Policy Decision Point: together, they establish trust, enforce authorization, and ensure authority continuity across agents, applications, and services.
Authority coreAgentic Trust Fabric
Distributed authority router
Permguard Trust Plane
All traffic is secured by the Agentic Trust Fabric. Destinations enforce authorization locally using the Policy Decision Point.
Enforce least privilege and continuous verification.
Purpose-built for agents, tools, and agent-to-agent flows.
Built for performance at the edge and across distributed systems.
Every decision and action is logged and verifiable.
AI agents / Transport
Permguard's security overlay enables real autonomous and distributed agents.
01 · TRANSPORT
AI agents need both synchronous and asynchronous communication across workflows, events, messaging, gRPC, and HTTP.As microservices taught us, distributed systems must tolerate failure while preserving authority continuity across every hop.
The Permguard Security Overlay applied agnostically at the transport layer.
02 · FRAMEWORKS
Every interaction runs through a governed, isolated execution.LangChain, Google ADK, Microsoft Agent Framework, Strands, and custom agents run inside a secure execution sandbox connected to the Agentic Trust Fabric.
Agents communicate securely inside an isolated Soglia execution sandbox.