A privileged position, treated as one.

These are properties of the system today.

Least privilege

Provider credentials are held by Verundo, never by the agent. An agent sees tools, not tokens, and only the tools it is granted.

Controlled execution

No action reaches a provider except through a protected action under policy. There is no bypass path for the agent.

Explicit approvals

Held actions execute only after a named person decides, and that decision is on the record with its reason.

Audit trail

Every run, action, approval, containment, recovery and observed external change is recorded, attributed to an agent identity and a model.

External verification

Recovery is confirmed by re-reading the external system, not by trusting an API response.

Data minimisation

Credential-looking values are masked before they are stored or shown. Verundo records what an action changed, not entire objects.

Idempotent execution

Every provider write carries an idempotency key, so retries and uncertain outcomes never duplicate a mutation.

Signed webhooks

Every inbound provider notification is signature-verified; the payload never decides state, only which object to re-read.

Marked plainly, because Verundo is not yet a multi-tenant hosted service.

Tenant isolation

Per-organisation data separation with row-level enforcement in the hosted product. Today Verundo runs as a single-tenant deployment per customer.

Encrypted secret vault

Per-tenant, KMS-backed storage for provider credentials with rotation. Today credentials live in the deployment's environment.

Configurable retention

Per-organisation retention windows for run records and before-states.

SSO and roles

SAML/OIDC sign-in and role-based approval rights.

Certifications

Verundo holds no SOC 2, ISO 27001 or similar certification yet. We will not claim one until an auditor has issued it.