Authenticated access
OIDC-based identity, personal access tokens and service-principal flows support authenticated access. RBAC controls administrative capabilities.
Sovereignty, security & trust
Sovereignty starts
with the boundary.
Swiss-based and vendor agnostic, AI Warden puts policy at the boundary of your AI stack. Review the hosted service, approved provider destinations, identity and evidence against your sovereignty requirements.
Deployment reviewGoverned
-
01
Identity & accessUsers, service principals and permissions
-
02
Credential custodyEncrypted provider credentials
-
03
Traffic handlingConfigured routing and inspection
-
04
Evidence & retentionRequest logs and governance records
Identity · Policy · EvidenceWorkflow illustration
Product security foundations
Explicit access.
Controlled operation.
Encrypted credentials
Provider and connector credential blobs are encrypted at rest. Deployments must manage the relevant key material and operational access.
Configured enforcement
Gateway policies control supported routed traffic. Content scanning and optional ICAP inspection operate within the configured request path.
Sovereignty by design
Control the path.
Know the responsibilities.
Hosting and residency
AI Warden is a hosted solution from a Swiss-based company. Agree the hosting region, data-residency requirements and applicable processing terms for your service.
Approved provider destinations
Choose supported model providers and MCP endpoints. Enforce access and configured inspection before routed requests leave the gateway. Provider processing locations and terms are part of the end-to-end sovereignty review.
Data exposure and evidence
Apply configured content controls and enterprise DLP to sensitive traffic. Set request-log body storage, retention and access to fit your evidence and data-handling needs.
Operational access
Review administrative access, support responsibilities, sub-processors and recovery arrangements as part of the hosted operating model.
Data handling
Review the data
the platform can touch.
Requests and responses
Model and MCP traffic routed through the gateway can be inspected. Logged bodies and metadata depend on the request-log storage configuration.
Identity and configuration
The control plane stores identities, registries, policies, approvals and encrypted credentials needed to operate the deployment.
Audit and retention
Administrative audit records and high-volume request logs serve different purposes. Review retention, body storage, access and evidence requirements during deployment.
Deployment responsibility
For hosted deployments, agree responsibility for networking, identity integration, backups, monitoring, upgrades and secret management. Self-hosted deployments use the customer's environment and operating model.
Enterprise review
Bring your questionnaire.
Discuss architecture, deployment boundaries, data processing and assurance requirements with our team.
See AI Warden in action
Make the security review concrete.
Walk through identities, data paths, logs, deployment and integration requirements with our engineers.