# Vault

For Vault, we use the [`kv engine`](https://developer.hashicorp.com/vault/docs/secrets/kv/kv-v2)  (version 2) for storing the credentials.  When creating your proxy, add the Vault information in order to connect your Secret storage to unSkript.

{% hint style="info" %}
Vault connectivity is only available in the full SAAS implementation, and not in the free Sandbox. Contact us for a demo.
{% endhint %}

<figure><img src="https://491011674-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm4p7lGuBAXN5jCVyoF7P%2Fuploads%2FeXq2aBPdwSvjwQDrXqBR%2FScreen%20Shot%202022-10-19%20at%2010.32.02%20AM.png?alt=media&#x26;token=9cf0ff50-c2b4-4e30-82ee-ba5617ab367a" alt=""><figcaption></figcaption></figure>

| Name                | Description                                                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Host                | Hostname of the vault server, along with the port number. For eg: *<https://vault.example.com:8200>*                         |
| Token               | Service Token to authenticate to Vault. This token should have CRUD access to the KV store.                                  |
| Mount Dir Name      | Path where the KV backend is mounted.                                                                                        |
| Vault Secret Prefix | User defined secret prefix to use when storing credentials. This prefix will be added to all the secrets added in the Vault. |