secret manager
A service that stores secrets centrally, controls who can read them and records every access.
In more detail
Examples are HashiCorp Vault and the secret services every cloud offers. Programs fetch a secret when they need it instead of keeping it in files, and rotating it in one place updates every reader.
Examples
Vault(POLICY).get("stripe-key", caller="billing") returns a lease and records the readThe course names five properties a secret manager adds over an environment variable: central storage with an owner, a policy per caller, an audit trail, versions for rotation, and short leases.In Terraform: Examples are HashiCorp Vault and the secret services every cloud offers. A Terraform configuration can read a secret from one at run time instead of keeping it in a file, ideally through an ephemeral resource so it never lands in state.Related terms
- AWS Secrets Manager — An AWS service that stores passwords, keys and other secrets encrypted and hands them to programs that are allowed to read them.
- secret lease — A borrowed copy of a secret that comes with an end time, after which it must not be used and a fresh copy must be fetched.
- secret version — One stored value of a secret; a manager keeps several and marks one as current, so rotation is a new version rather than an overwrite.
- audit trail — A record of who did what and when, kept so actions can be reviewed and investigated later.
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
- workload identity — An identity for software rather than a person, proven by a signed token from the platform it runs on instead of a stored key.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- HashiCorp Vault — HashiCorp's secret manager, which stores passwords and keys centrally and can hand out short-lived credentials on request.
- ephemeral values — Values, added in Terraform 1.10, that exist only during a run and are never written to state or plan files.
Taught in
- The Environment Variable Trap — Application Security & Threat Modeling for Engineers
- Moving To A Secret Manager — Application Security & Threat Modeling for Engineers
- Workload Identity — Application Security & Threat Modeling for Engineers
- Secret Scanning — Application Security & Threat Modeling for Engineers
- Parameterising With Input Variables — Infrastructure as Code with Terraform
- Security: Secrets In State And Ephemeral Values — Infrastructure as Code with Terraform