Glossary

Secrets management

secret management

Definition

Secrets management controls how software credentials and other sensitive keys are stored, accessed, replaced and revoked.

It manages sensitive software credentials from creation to revocation, including storage, access, auditing and replacement. Permissions and rotation still need to match each system's risk.

A customer may include “Secrets management” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

Secrets management covers the lifecycle of credentials used by software, including database passwords, private keys and confidential API keys. It aims to make those values available to authorised applications without scattering them through source code, shared documents or employee messages.

A secrets manager can store values centrally, record access and deliver credentials to applications. Some systems can generate short-lived credentials or rotate stored ones. The surrounding permissions matter: an application that can retrieve every secret still has excessive access, even if the vault encrypts them.

Consider a small software company connecting its website to a payment provider. A dedicated secret store can supply the required credential to the application at runtime. Developers do not need to paste the production credential into the code repository or a team chat.

The difficult part is often replacement. Changing a credential without updating every dependent service can cause an outage; leaving an exposed credential active can allow misuse. Establish ownership, test the replacement process and plan emergency revocation. A secrets manager must itself have protected administrator access and a recovery arrangement. It reduces secret sprawl but does not remove the need to design access carefully.

Sources