Secrets management

Secrets management is the practice of securely handling the credentials that machines, applications, and infrastructure use to authenticate to one another. Unlike a user password typed at login, these secrets are consumed by code and automation — so they need to be stored, delivered, rotated, and audited in ways suited to systems rather than people.

Secrets are the non-human credentials that hold systems together:

• API keys and tokens used by applications and integrations.
• Database connection strings and passwords used by services.
• Certificates and private keys used to establish trust.
• Service account credentials used by automation.
• Encryption keys used to protect other data.

A secrets management system centralizes control of these credentials:

• Secure storage — secrets are held encrypted in a central vault, not hard-coded in source or config.
• Controlled distribution — applications retrieve secrets at runtime through authenticated requests.
• Rotation — secrets are changed regularly, ideally without downtime.
• Auditing — every access to a secret is logged.

Password management deals mainly with human credentials — the passwords people use to log in. Secrets management deals with non-human credentials that applications and infrastructure use to authenticate automatically. The challenges differ: passwords are entered by people, while secrets are consumed by code at scale and speed, which puts a premium on programmatic retrieval and automated rotation.

Secrets hard-coded in source code, configuration files, or scripts are a common and dangerous exposure — they leak into repositories, logs, and backups, and rarely get rotated. Centralizing them removes those hiding places, allows rotation without code changes, and makes every use auditable, closing one of the most overlooked gaps in an organization's credential security.