Member-only story
Why I Run Multiple SSH Keys Instead of Just One
--
Share
For many Linux admins, a single SSH key pair is the default for logging into every server, staging box, or cloud instance they own. It’s simple, convenient — and a single point of failure.
Over time, I’ve learned that separating SSH keys by purpose and environment isn’t just good hygiene — it’s a major security win.
🛑 The Risk of “One Key to Rule Them All”
If you use the same SSH private key for everything, one compromise can be catastrophic:
- Lose your laptop? Every server that key touches is now at risk.
- Key is stolen from a less-secure environment? Attackers can pivot into critical systems.
- Need to rotate keys? You’re now scrambling to replace it everywhere.
This is the definition of a blast radius problem.
🧩 How I Segment My Keys
I maintain separate SSH keys for:
- Production
- Stored in a hardware token or secure key vault
- Only used for critical servers
- Never leaves secure devices
- Staging/Test
- Separate from production