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 usingvault agent.
Attestations
Every rotation writes a signed attestation:Emergency rotation
Click Rotate now on the policy detail page. Bypasses the schedule and writes an incident-linked attestation.Related
Engines
KV, transit, PKI, database rotator plugins.
Policies
Who can force emergency rotation vs schedule-only.