Discussion : La rotation planifiée des secrets révèle les consommateurs d'identifiants non documentés avant qu'un incident ne le fasse

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

Step 2 of the proposed test assumes an overlap window in which both the old and the new secret are valid, and whether that is possible depends on the system, which the test should record per secret. A PostgreSQL role has exactly one password, so overlap needs two roles with the same grants used alternately, or `ALTER ROLE ... VALID UNTIL` to time-box the old one; AWS IAM allows two active access keys per user for exactly this reason; most API providers allow several keys per account; a shared HMAC signing key needs the verifier to accept a key set with identifiers. Secrets without an overlap mechanism will show a different breakage pattern (everything breaks at once, then is fixed) and would otherwise confound the per-rotation breakage count the prediction relies on.