Navigation
Vault access. Public access is not open. This product is separate from initial Identity and Apparatus access.
Screenshots use fictional demonstration accounts. Your data and available actions may differ. Reviewed October 16, 2026.
Security and limits
Security
Access status
Vault is not included in the initial public rollout. This page describes reviewed behavior. The current deployment uses LocalKms; it does not establish a cloud-KMS or hardware-backed deployment assurance.
Encryption and key management
The implementation uses XChaCha20-Poly1305 authenticated encryption. The local provider uses a configured master key. The Google Cloud KMS provider wraps per-credential data keys and encrypts credential values locally. The selected provider and operational controls depend on the deployment.
Earlier documentation described AES-256-GCM, a universal tenant key hierarchy and mandatory HSM storage. Those claims do not match the reviewed implementations. See Encryption Envelope.
Transport and access
The MCP surface uses remote Streamable HTTP at /api/mcp. It is not the previously documented local stdio package. Authorized clients must use the approved HTTPS deployment and its supported authentication flow. Tenant checks, roles and credential scope restrict access.
Leases and plaintext
A lease is attributed, time limited and single use when redeemed. Expiry or revocation prevents a future redemption. It does not erase a value already returned, invalidate an API key at its issuer, or remove a secret from model context or logs.
The MCP read tool returns plaintext by default. Reference responses require explicit client integration and verification of the downstream secret-handling path. See Credential references.
Audit integrity
The implementation records security events in a per-tenant hash chain and provides integrity verification. This makes covered modifications detectable; it is not a guarantee against a fully compromised operator or storage system. Retention and export behavior must be checked for the deployment.
Security review and reporting
No public penetration-test report, certification, customer response SLA or hardware-backed deployment assurance is established by this documentation. See Compliance status. Contact hello@ghoststack.app to arrange a private report without sending credentials or sensitive evidence in the initial message.
Screen reference
