An engine is a mounted secret backend at a path. TigerTrust ships Vault-compatible engines — enable them per workspace, then use them via the vault CLI or any Vault-compatible client.

Supported engines

TypePath conventionWhat it does
kv (v2)secret/Versioned static secrets
kv (v1)kv/Simple key-value
transittransit/Encrypt / decrypt as a service, key rotation
pkipki/Issue X.509 leaf certs
databasedatabase/Dynamic short-lived DB credentials
wrapping(implicit)Single-use response wrapping

Enable an engine

vault secrets enable -path=secret kv-v2
vault secrets enable transit
vault secrets enable pki
vault secrets enable database

KV v2

vault kv put  secret/prod/db/password value=hunter2
vault kv get  secret/prod/db/password
vault kv get  -version=1 secret/prod/db/password
vault kv list secret/prod/db

Transit

vault write transit/keys/prod-payments type=aes256-gcm96
vault write transit/encrypt/prod-payments plaintext=$(base64 <<< "card")
vault write transit/decrypt/prod-payments ciphertext=vault:v1:...
vault write -f transit/keys/prod-payments/rotate

PKI

vault write pki/root/generate/internal \
  common_name="TigerTrust Internal Root" ttl=87600h

vault write pki/roles/web-server \
  allowed_domains=example.com allow_subdomains=true max_ttl=90d

vault write pki/issue/web-server common_name=web.example.com
The PKI engine can be chained to CLM’s PKI Core as its issuer.

Database

vault write database/config/prod-postgres \
  plugin_name=postgresql-database-plugin \
  connection_url='postgres://root:...@db:5432/postgres' \
  allowed_roles=prod-postgres

vault write database/roles/prod-postgres \
  db_name=prod-postgres \
  default_ttl=1h max_ttl=24h \
  creation_statements="CREATE ROLE \"{{name}}\" WITH LOGIN PASSWORD '{{password}}' VALID UNTIL '{{expiration}}'; GRANT read_only TO \"{{name}}\";"

vault read database/creds/prod-postgres

Rotation

Automate KV and DB rotation on a schedule.

Policies

Restrict who can read/write which paths.