Permguard provides traditional application authorization through Policy Decision Points, together with a security overlay for the agentic era.
Trust-anchored protocol
Identity enters a protected execution tunnel. Trust anchors operate inside it, its boundaries enforce the guardrails, and the protocol at its exit constrains the final decision.
Trust, authorization, and isolated execution—one system for governing agents, applications, and services.
Permguard / Trust
01The security overlay for the agentic ecosystem.
Secure agents, tools, and agent-to-agent interactions with Provenance Identity Continuity (PIC) and the Permguard Trust Plane.
Permguard / Authorization
02Authorization for services and applications.
A Policy Decision Point designed for enterprise applications and built for Zero Trust, resilience, full auditability, and distributed systems.
Execution layer / Soglia
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.
Explore SogliaPhilosophy
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.
Stated
every guarantee is a formal property, not a promise
Proved
it holds along the whole causal chain of an execution
Enforced
Permguard supplies exactly what the proof assumes
“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.
What the verifier can see
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.
Theorem 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.
Theorems 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.
Model-level results, under the assumptions stated in the paper.
Unified Governance
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.
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.
