What is AgentSecrets?
The Zero-Knowledge Difference
How AgentSecrets Works
Installation
Quick Start
Migrating from .env Files
Migrating from Vault / AWS
Migrating from dotenv-vault
Production Checklist
Credential Exposure
What Zero-Knowledge Means
The Proxy Model
The Three-Layer Model
Environments
Agent Identity
Storage Modes
The No get() Principle
Secret-Level Policies
Cloud Overview & Architecture
The Dual-Engine Model
Cloud Resolver Data Plane
Workload & Agent Tokens
Egress Allowlists & Audit Streams
Cloud REST API Reference
Account (init / login)
Server & Self-Hosting (server)
Docs
Shell Autocompletion
Keychain Auth
Secrets
Environments
Credential Proxy
env Injection
Workspaces & Teams
Projects
Agent Identity
Audit & Governance
Integrations Overview
Claude Desktop
Cursor
OpenClaw
HTTP Proxy (Any)
LangChain (Soon)
CrewAI (Soon)
CI/CD Pipeline
SDK Overview
Python SDK
Python API Reference
Python SDK Manual Testing
JavaScript SDK (Soon)
Ecosystem Overview
Zero-Knowledge MCP Server
Server Overview
5-Layer Architecture
Self-Hosting Guide
Authentication & Keys
Workspaces & Teams
Projects & Scope
Environments
Secrets & Sync Protocol
Agent Identity Resolution
Telemetry & Metrics Engine
Audit Log Sync
API Endpoint Reference
Security Overview
Anti-Impersonation & Process Verification
Encryption Model
Zero-Knowledge Sync
Proxy Security Layers
Threat Model
OWASP Top 10 Mitigation
Security FAQ
Third-Party Audit
Reporting Vulnerabilities
Guides Overview
Building on the SDK
Stripe Integration
OpenAI Integration
Multi-Agent Setup
Onboarding Team
CI/CD Pipeline
Publishing ZK MCP
Rotating Credentials
Auditing Team Activity
Dev to Production
Kubernetes Deployment
Monorepo Setup
Production Proxy Hardening
vs .env Files
vs HashiCorp Vault
vs AWS Secrets Manager
vs dotenv-vault
vs Infisical
When Not to Use
Proxy Not Starting
Proxy Not Resolving
Domain Blocked
Sync Conflicts
MCP Not Connecting
Session Token Errors
Proxy Session Authorization
Keychain Storage & Backends
SSRF & Destination Rules
Installation Issues
Error Codes Reference
Frequently Asked Questions
v3.1.x
v3.0.0
v2.1.0
v2.0.0
v1.4.0
v1.3.x
v1.2.0
v1.1.x
v1.0.x
CLI ReferenceUsing for Compliance

Compliance & Certifications

AgentSecrets is designed from the ground up to satisfy the strictest compliance regimes, including SOC 2 Type II, ISO 27001, HIPAA, and GDPR.

By eliminating credential exposure in process memory and generating immutable access logs, AgentSecrets simplifies your compliance audits.


Access Control & Principle of Least Privilege

Traditional setups often grant broad access to .env files. AgentSecrets enforces granular, role-based access control (RBAC):

  • Project Isolation: A compromised AI agent in the support project cannot access secrets in the billing project.
  • Environment Isolation: production credentials are cryptographically separated from development credentials.
  • Domain Allowlists: The network boundary actively prevents data exfiltration by denying outbound connections to unauthorized domains.

Data Encryption

Encryption in Transit

All synchronization traffic between the AgentSecrets CLI and the AgentSecrets Cloud API is secured using TLS 1.3.

Encryption at Rest (Client-Side)

AgentSecrets employs a strict Zero-Knowledge architecture:

  1. Your workspace encryption key never leaves your local OS Keychain.
  2. Credentials are encrypted locally using AES-256-GCM.
  3. The AgentSecrets server only receives, stores, and synchronizes the resulting ciphertext blobs. This structural guarantee means that in the event of an AgentSecrets database breach, your credentials remain mathematically secure.

Audit Logging

For SOC 2 and ISO 27001 compliance, you must prove who accessed what data and when.

AgentSecrets provides transport-layer audit logs for every API call made by an agent. The logs include the agent identity, target domain, timestamp, and key reference, fulfilling non-repudiation requirements without exposing the credential value in the log stream.

Was this helpful?
Thanks for your feedback!
Your feedback helps us improve the platform.