Credential Rotation, Explained for Non-Engineers
“We rotate credentials” sounds like jargon, but the idea is simple and worth understanding even if you never touch a server. It’s one of the highest-value security practices almost nobody outside engineering hears about, and when it’s automatic, it protects you without any effort.
What a credential is
A credential is anything that proves “I’m allowed in”, a database password, an SSH key, an API token. Your site uses several of them behind the scenes to connect its parts together. They’re the keys to the building, and like keys, they can be copied or lost.
Why they leak
Credentials leak in mundane ways: accidentally committed to a public repository, exposed in a log, reused from a service that got breached, or left on a former contractor’s laptop. Often nobody knows it happened. A leaked credential is dangerous precisely because it keeps working silently.
What rotation does
Rotation replaces credentials with new ones on a regular schedule. The old ones stop working. So even if a password leaked last month and you never found out, it expires on its own, the leak has a short shelf life instead of an indefinite one. It doesn’t prevent leaks; it limits how long a leak is useful.

Why it should be automatic
Manual rotation is the kind of chore everyone agrees is important and nobody does. Automating it on a schedule is the only version that actually happens. On SrvBot, credentials rotate automatically on a regular schedule, without anyone lifting a finger.
The bottom line
You don’t need to understand the cryptography to benefit from rotation, you just need it turned on. It quietly shrinks the damage a leak can do. See how ours works across /help.