Built for enterprise trust.
How we handle data, credentials, access and incidents — in plain language, no compliance theater. Everything on this page is in the public documentation.
Six security pillars
Explore the controls and documentation for each layer. Configuration and scope need to be assessed for your implementation.
Encryption and vault
The vault protects integration credentials with AES-256-GCM encryption. Configure secure transport and access for each service according to your implementation architecture.
View documentationTenant isolation
Agents, data and credentials are organized by tenant, with access controls in the application and database. Review permissions and integrations against company requirements.
View documentationBYOK — your key, your control
Use your own keys from supported providers. Routing and fallback follow the models, permissions and resources enabled for your account.
View documentationOn-premise without VPN
Zihin Tunnel initiates an outbound connection to access authorized services in your network. Service scope, authentication and credential handling are part of the configuration.
View documentationRBAC — roles and permissions
Roles and permissions control access to platform functions. Define who can configure agents, operate tools and view records for each context.
View documentationAudit and telemetry
View sessions, tool calls, costs and latency in the available records. Coverage and retention depend on your operational configuration.
View documentationPolicies the agent cannot ignore
Contextual Security Policies (CSP) are enforced on every execution — not a PDF of good intentions. Five types cover the full cycle, and guardrails like iteration limits and tool blocking are enforced by the runtime, not merely suggested to the model.
Schedule
Restrict when the agent operates: business hours, weekdays, timezone. Outside the window, it doesn't run.
Behavior
Tone, language, must-dos and must-nots — including blocking specific tools and iteration limits enforced by the runtime.
Data
Access restrictions on sensitive fields and entities — the agent only touches what policy allows.
Origin
Restrict where the agent can be triggered from: allowed IPs and domains.
Custom
Your own rules in flexible JSON for whatever is specific to your operation.
Scope inheritance
Policies flow from broad to narrow scope — the most specific wins. Define once at tenant level, refine per team, agent or user.
tenant → team → agent → user
Full types, scopes and rule examples are in the documentation: Contextual Security Policies
Questions every security team asks
Where are my systems' credentials stored?
In the platform vault, encrypted with AES-256-GCM — never in configuration files or schemas. With Zihin Tunnel it's even better: internal systems' credentials are resolved inside your network and never leave it.
Do I need to open firewall ports to connect my ERP?
No. Zihin Tunnel uses an outbound WebSocket connection on port 443 (same as your browser). No inbound ports, no VPN, no firewall changes.
Can I use my own OpenAI or Anthropic key?
Yes. BYOK lets you use your own keys from supported providers. Models, consumption and fallback depend on your account configuration; confirm the intended behavior before putting an agent into operation.
How do I control what an agent can and cannot do?
Two layers: RBAC controls what people and API keys can do on the platform; Contextual Security Policies (CSP) control what the agent can do at runtime — schedule, behavior, data, origin — with runtime-enforced guardrails like tool blocking and iteration limits.
What gets recorded for each execution?
The full session: phases, tool calls, tokens, costs and latencies. All queryable in the console and via the telemetry API — auditing isn't an optional feature, it's the default.
I found a vulnerability. How do I report it?
Write to contact@zihin.ai with the subject [security]. We respond within 72 hours, validate the proof of concept and coordinate disclosure. Good-faith researchers face no retaliation.
Compliance and corporate governance questions? See the Enterprise page
Responsible vulnerability disclosure
If you found a vulnerability, write directly to contact@zihin.ai. We commit to responding within 72 hours, validating the proof of concept and coordinating disclosure. We do not weaponize copyright or fraud laws against researchers acting in good faith.
contact@zihin.aiDue diligence underway?
DPA, security questionnaires and conversations with our engineering team.