PRODUCT IN DEVELOPMENT ↗HUMAN AUTHORITY. BY DESIGN.
AI SECURITY / ACTION-LEVEL BOUNDARIES

Intelligence has a purpose.
Authority has a boundary.

An AI agent needs an owner, a scope and controls it cannot overrule. Explore the separation between reasoning and permission.

OMNIGUARD / AI SECURITYPRODUCT IN DEVELOPMENT

Try changing
the request.

Choose a permission on the passport. Then add a persuasive instruction. In this sample, the policy boundary does not change.

This illustrates deterministic permission checks. It is not a claim of perfect injection detection, model alignment or universal enforcement.

Investigate agent misuse
AI PASSPORT
SPECIMEN / 086
SANDBOX POLICY
AGENT IDENTITY

invoice-assistant

Owner: Finance · Scope: invoice processing

> invoice.read

Allowed by the invoice-reader scope. The agent can read this invoice, not the whole organisation.

The policy, not the request’s wording, decides the permitted scope. This is a scripted demonstration.
01

Start with accountable agent identities.

The AI Passport is a proposed policy record, not a visual badge that makes an agent safe. It should identify the owner, intended task, allowed tools and resources, data limits, network destinations and expiry.

Permission changes need an audit trail. Credentials must not be shared across unrelated agents or customers. Higher authority should never follow simply from a model asking for it.

02

Enforce where the action actually happens.

Requests must pass through a non-bypassable, appropriately authenticated tool boundary. A convenient SDK wrapper is not sufficient if an agent also holds direct production credentials.

Approval should bind to the exact target and operation. “Allow a payment draft” must not become “allow any payment”. Parameters, destination and amount need revalidation immediately before execution.

03

Treat outside content as data, not authority.

Documents, web pages and tool responses can carry misleading instructions. Content screening may contribute evidence, but it cannot be the sole security boundary.

The planned approach layers least privilege, resource restrictions, input and output validation, data controls, behavioural evidence and human review. These controls still require testing against actual integrations and failure cases.

04

Model choice should not choose your permissions.

The intended gateway is independent of the model provider. A hosted model, a local model and a customer-selected model should still face the same application-side authority checks.

Model processing, redaction, prompt retention and any external provider must be disclosed before deployment. This website’s demo uses no model and transmits no prompts.

THE NEXT CHAPTER OF CONNECTED DEFENCE

Less noise.
More understanding.

Explore the idea. Challenge the assumptions.
Help shape what comes next.

Explore early accessDEVELOPMENT STAGE · NO PAYMENT REQUIRED
PlatformAI securityIntegrationsTrustPricingInteractive demoEarly accessCompanyContactPrivacyWebsite terms
OMNIGUARD / QUICK NAVIGATION ↑ ↓ NAVIGATE · ENTER OPEN