Service-to-Service Credential Rotation Failure

A routine service-to-service credential rotation is in progress between Service A, Service B, Service C, the Secret Manager, and the Certificate/Token Issuer. Four business invariants govern every decision here: (1) service-to-service calls must remain authenticated throughout the rotation — a credential gap must never be bridged by disabling authentication; (2) old and new credentials may overlap in validity for a bounded window — this is the safe mechanism this rotation is built around, not a risk to eliminate early; (3) revoking the old credential before all workloads have confirmed rotation creates a real outage, not just a security exposure; (4) rotation cohorts may be staged — broad instant rotation across every workload simultaneously is not required and is not necessarily safer. The scenario's required security invariant: a revoked credential must never be silently re-accepted merely to restore connectivity — if revocation was premature, the fix is re-extending validity deliberately and auditably, never bypassing credential validation. Decide how to sequence activation of the new credential, how to stage and verify cohort adoption before revoking anything, and — if a premature revocation gap is ever created — whether to close it the sanctioned way or reach for the tempting but forbidden broad authentication bypass.

Difficulty

Senior Staff

Expected Time

~20 min

Category

Security & Identity