A rotation policy attaches a schedule and a rotator plugin to a secret path. When the schedule fires, SM rewrites the value, invalidates the old lease, and writes a signed rotation attestation to the audit stream. Rotation policies are a TigerTrust extension on top of the Vault-compat surface — configure them from the UI at Settings → Secrets Manager → Rotation or via REST.

Create a rotation policy (KV)

Settings → Secrets Manager → Rotation → New policy. Pick a KV path, a schedule (cron or @daily/@weekly), and a rotator (random-string, random-hex, pgp-passphrase, etc.).

Create a rotation policy (database)

Database engines rotate at the role level — SM issues a fresh username/password from the DB and revokes the previous one. Configure under Settings → Secrets Manager → Rotation → New policy → Database. Every dynamic credential inherits the current root — rotate the root and every issued credential is revoked and re-minted transparently to callers using vault agent.

Attestations

Every rotation writes a signed attestation:
{
  "policy_id":  "rp_xxx",
  "path":       "secret/prod/db/password",
  "previous_version": 12,
  "new_version": 13,
  "rotated_at": "2026-09-18T02:00:00Z",
  "signature":  "sig:v1:..."
}
The attestation is retrievable from the policy detail page in the UI and satisfies the “prove this secret was rotated within N days” line item on most audits.

Emergency rotation

Click Rotate now on the policy detail page. Bypasses the schedule and writes an incident-linked attestation.

Engines

KV, transit, PKI, database rotator plugins.

Policies

Who can force emergency rotation vs schedule-only.