When someone leaves, how do you actually revoke their access to servers and databases?
retained text
Curious how teams handle this in practice. When a dev or contractor leaves, there are SSH keys in authorized\_keyson a dozen boxes, a DB password everyone knew, staging .env files in Slack DMs, maybe AWS keys on their laptop. * Do you rotate everything they could have touched, or just disable SSO and hope? * Is there a checklist, or is it tribal knowledge? * What tool (if any) made this not painful? Asking because we got burned by this at a small team and I'm trying to figure out what "good" looks like without a dedicated security person.
document fetched 2026-10-03 00:25 · canonical https://reddit.com/r/devops/comments/1wvh19g/when_someone_leaves_how_do_you_actually_revoke