Secrets dans un coffre, rotation sans interruption, accès audités.
Spec — Secrets rotation
Status: draft · Created: 2026-11-10
1. Context and goal
Passwords, keys and tokens live in one vault, change regularly without breaking services, and every read is traceable.
2. Functional requirements (EARS)
- FR-1: THE SYSTEM SHALL keep every secret in the vault, with no secret in source code, images or plain environment files, checked by a secret scanner in the pipeline.
- FR-2: THE SYSTEM SHALL give each service access only to the secrets it needs, with credentials that expire within 1 hour.
- FR-3: THE SYSTEM SHALL rotate database passwords and API keys at least every 90 days.
- FR-4: WHILE a secret is being rotated, THE SYSTEM SHALL accept both the old and the new value for up to 1 hour, so no request fails.
- FR-5: WHEN a secret is suspected leaked, THE SYSTEM SHALL let an operator revoke and replace it within 15 minutes.
- FR-6: THE SYSTEM SHALL audit every read and change of a secret with the identity, the secret name and the time, kept for 1 year.
3. Out of scope
- Rotation of end-user passwords.
- Hardware security modules.