Secrets Management
Centralized, controlled storage and delivery of credentials and keys.
What it is
The discipline and tooling for storing, distributing, rotating, and auditing sensitive values such as passwords, tokens, and keys, so they are not scattered through code or config. Access is brokered and logged rather than copied around.
Why it matters
Poor secret handling is a recurring breach cause, and a centralized store gives responders both an access audit trail and a single place to rotate everything once exposure is suspected.
In practice
After a compromise, the team rotates every credential from the central secrets store and uses its access log to see which the attacker had retrieved.
What to look for
- Secrets in code, config files or environment variables.
- Secrets that never rotate or are shared across environments.
- Unusual reads of many secrets by one identity.
Common mistake
Storing the vault token next to the app it protects. The secret store is only as safe as the credential that opens it.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
HashiCorp Vault Source available
Stores secrets centrally and hands out short lived credentials.
-
AWS Key Management Service Cloud service
Keeps master keys in hardware and logs every use to CloudTrail.
-
Trivy Open source
Finds secrets accidentally left in images and code.
Read next
- Key Management and Envelope Encryption: Managing encryption keys and wrapping data keys with protected master keys.
- Access Keys: Static, long-lived credential pairs used to authenticate to cloud APIs.
- Service Account: A non-human identity used by an application or workload, not a person.