Security at a glance
Encrypted per organization
Each organization’s secrets are encrypted with AES-256-GCM using a data key that belongs to that organization only. Data keys are themselves encrypted by a master key that is never stored in the database.
Write-only secrets
No screen, email, or API response ever returns a secret after it is saved — not even part of it. Secrets are decrypted only on the server, at the moment a connector needs them.
Two-factor to open
Admins open the Vault with a fresh code from their authenticator app. The unlock is bound to that single session and ends after one hour at most.
Every admin is informed
Every applied change and every lockout is recorded in the Vault history and emailed to all admins in the organization.
How secrets are protected
- Separate keys. A database backup on its own contains only encrypted secrets and encrypted data keys. Reading a secret also requires the master key, which is kept separately in a secret manager.
- Server-side use only. When a member connects through the Vault, the connector points to the secret instead of holding a copy. DeepMask’s servers read the secret when the connector needs it and never send it to a browser.
- Fixed destinations. For Custom MCP servers, the server URL is part of the secret. Members can’t change it, so your organization’s key is only ever sent to the server an admin chose. The URL must be a public address; private and internal network addresses are refused.
- Fail closed. If the Vault can’t verify its configuration, it stays unavailable instead of running in a weaker mode. The rest of DeepMask keeps working.
How admin access is protected
- Two-Factor Authentication is required. It must be turned on for the organization, and the admin needs an authenticator app. Recovery codes, emailed codes, and “remember this device” never open the Vault.
- Fresh sign-in after setting up an authenticator. A session that started before the admin’s authenticator was set up can’t open the Vault. This stops someone with a stolen session from adding their own authenticator.
- Single-use codes. Each authenticator code works once.
- Session-bound unlock. An open Vault applies only to the session where the code was entered and ends after one hour, at sign-out, or when the admin selects Lock Vault.
- Continuous checks. Every request re-checks the admin’s role and two-factor status. An admin who is demoted or turns off two-factor loses access immediately, even inside an open Vault.
- Lockouts. 10 wrong codes within an hour lock that admin out of the Vault for one hour and notify every admin.
Changes that need extra approval
Once your organization has at least one Vault secret, some actions outside the Vault could be used to gain Vault access. These actions always ask for a fresh authenticator code, even if the Vault is open:- Promoting a member to admin.
- Inviting someone as an admin.
- Turning off Two-Factor Authentication for the organization.
Only Vault-eligible admins can approve these actions. If you see You cannot approve security changes yet, open Settings → Vault to see which requirement is missing.
How member access is controlled
- Members see only a secret’s name — never its value or any part of it.
- Each use is checked against the secret’s status and access list. Disabling a secret, restricting its access, or removing a member from the organization stops the connection at its next sign-in or token refresh.
- For Salesforce and Microsoft, each member still signs in with their own account and keeps their own permissions at the provider.
Revocation isn’t instant. A token issued before a change can keep working until it expires — usually about an hour, longer for Salesforce sessions. To cut off access immediately, also revoke the credentials or the user’s sessions at the provider.
If something looks wrong
Act quickly if a Vault email reports a change nobody on your team made, or a lockout nobody caused.1
Contain the account
Sign the affected admin out of all devices and reset their password. If you can’t reach them, remove their admin role.
2
Check the history
Open Settings → Vault → History and review recent unlocks and changes for that admin.
3
Rotate exposed credentials
For every secret that may have been changed, create new credentials at the provider, then use Replace credentials in the Vault and revoke the old credentials at the provider.
4
Contact DeepMask
Email contact@deepmask.io with the time and the admin involved so we can help investigate.
Related pages
Security and compliance
DeepMask’s hosting, encryption, and GDPR commitments.
Open the Vault
Requirements, unlocking, and lockouts.