Secure Vault for Teams
Secure Vault for Teams

Connecting to the vault…

The page is requesting the encrypted data. Nothing is decrypted before you enter the master password.

Team credentials, encrypted before they leave the browser.

  • One master password opens the vault. It is shared by the team and is not stored anywhere, not even on this page.
  • Every entry is encrypted with AES-256-GCM on your device. Title, username, group and notes included: the databasethe git repository only ever receives ciphertext.
  • The vault locks itself. After a few minutes without activity, or when the page is reloaded, it asks for the master password again.

Security and limits

What this vault protects

  • The master password never leaves the browser. A key is derived from it with PBKDF2-SHA-256, 600,000 iterations.
  • That key unlocks the vault key (AES-256), which encrypts each entry with AES-256-GCM. The artifact database only stores ciphertext.
  • Only accounts with Contributor access or higher can read that ciphertext. Visitors and read-only accounts do not receive it.
  • Attachments are encrypted in chunks with the same key, before they leave the browser. The name and exact size of each file stay inside the encrypted entry: the database only sees how many chunks there are.
  • That key unlocks the vault key (AES-256), which encrypts each entry with AES-256-GCM. The portal server and the git repository only store ciphertext: one file per entry and per attachment chunk.
  • The portal only hands that ciphertext to those who present the access key. Every change is a commit pushed to the repository; if the push fails, nothing is saved.
  • Attachments are encrypted in chunks with the same key, before they leave the browser. The name and exact size of each file stay inside the encrypted entry: the repository only sees how many chunks there are.
  • The key is kept in memory only and is discarded on lock, on reload or after inactivity.

What it does not protect

  • Anyone with Editor access to this artifact can publish a modified version of this page. Give that level only to those who administer the vault.
  • A Contributor can delete or replace entries even without the master password. Export backups regularly.
  • Whoever administers the portal server can serve a modified version of this page. The portal must sit behind HTTPS, on a server the team trusts.
  • Anyone who has the access key, or can write to the repository, can delete or replace entries even without the master password. The git history makes it possible to revert.
  • Anyone who can read the repository can try to guess the master password with no limit on attempts. Keep it private and the password long.
  • Git keeps everything: deleted entries and old versions remain in the history, encrypted. Changing the master password does not re-encrypt the data: anyone who knew an old one and has access to the repository can still open the vault.
  • Commits show, unencrypted, when each file changed. There are no individual accounts: the portal does not know who made each change.
  • The master password is shared. When someone leaves the team, change it and rotate the credentials that person knew.
  • A downloaded attachment sits decrypted on your device, outside the vault. Delete it when it is no longer needed.
  • The git export only contains ciphertext, but a repository keeps the whole history: deleted entries are still there, and anyone who knew an old master password and has access to the repository can still open what is in it. Keep the repository private.
  • There is no recovery: without the master password, the data is lost.
  • This vault has not been audited by a third party.

Git repository

The vault data lives in this repository, always encrypted. The address and the branch are set in the docker-compose.yml of the portal.

Address
Branch
Last commit
Synchronisation
Commit author
Shown in "last changed by", inside the encrypted entry. It is stored in this browser only.

Change the master password

The entries are kept. Anyone who already had the vault open carries on working and will need the new password at the next unlock.

In the git repository, the old password still opens the versions kept in the history, and with them the current vault key.

Minimum of 14 characters.

Password generator

20