Secrets management
Secrets — database credentials, encryption keys, access tokens — are
among the most sensitive assets of any platform. In Dyncloud they are
managed with a dedicated secrets manager.
Principles
- Never in plaintext: secrets are not stored in code, configuration
files, or plain text. They live encrypted in the secrets manager.
- Minimal, on-demand access: each component obtains only the
secrets it needs, and only at the moment it needs them.
- Centralized custody: there's a single point of custody and control,
instead of scattered credentials.
- Rotation: secrets can be rotated (renewed) without having to
rebuild the system, which limits the window of usefulness of a
compromised credential.
- Traceability: access to secrets is logged.
Credential separation
Each environment has its own credentials. One environment's
credentials don't work to access another, which reinforces
isolation between environments.
Why it matters
Most serious breaches start with a leaked credential. By keeping
secrets encrypted, handing them out only to those who need them, and
being able to rotate them, we reduce both the likelihood and the
impact of that scenario.