Secrets Management
The controlled creation, storage, distribution, use, rotation, revocation, and auditing of sensitive credentials used by people, applications, and infrastructure.
It reduces hard-coded credentials, uncontrolled copies, long-lived access, and incident-response delays. Strong secrets practices are essential for cloud infrastructure, APIs, automation, and CI/CD.
A deployment pipeline authenticates through workload identity and retrieves a short-lived database credential at runtime instead of storing a password in source code or environment files.
A vault is not sufficient if applications log secrets, identities are overprivileged, recovery is weak, or rotation breaks dependent systems. The management platform itself becomes a critical security dependency.
Secrets include passwords, API keys, tokens, certificates, and cryptographic keys. A secrets-management system centralises protected storage, authenticates workloads, issues narrowly scoped or dynamic credentials, limits exposure, records access, and automates rotation.
Systems Architecture
OWASP Secrets Management Cheat Sheet — https://cheatsheetseries.owasp.org/cheatsheets/Secrets_Management_Cheat_Sheet.html; NIST SP 800-57 Part 1 — https://doi.org/10.6028/NIST.SP.800-57pt1r5
