Re:Advent of Sysadmin 2025
by hnlmorg on Monday December 01, 2025 @04:14AM
(#46105201)
Please don't take this as trivialising your issues. But some potential solutions here might be:
> Get a user to stop logging in as root.
Change root password and take them out of sudoers.
> Get all users to stop sharing the same login and password for all servers.
Switch to SSH certificates. It's going to be an initial moment of pain getting everyone set up with private certificates, but ones it's done there wouldn't be any passwords to share.
If you want to get clether, you can even pull SSH public keys from AWS SSM, or Github, or somewhere elsewhere, so that you don't need to manage these certificates yourself.
Then add to the company IT policy that sharing private certificates is a fireable offence.
> Get a user to use configuration management rather than scp'ing config files from their laptop to the server.
Disable `scp` in the sshd_config for that user
> Get a user to stop keeping one file with all production secrets in S3, and use a secrets vault instead.
AWS has some security tooling here that might help. Though you're not going to get that for free.
> Get a user to stop using the aws root account's access keys for their application.
Just remove the keys. Ideally you'd want them to set up OAuth before hand but even a user access key would be better.
Then add hardware MFA on the root account and notification to Slack/Teams/Email you when someone does try to access it.
> Get management to give you the authority to force users to rotate their AWS access keys which are 8 years old.
AWS Security Hub is free for 30 days, so enable that and then show management the failing items. You're now presenting evidence from an authority (AWS, plus CIS, NIST, whoever if you chose to enable their frameworks too) rather than arguing about what management might perciese as your own personal opinion.
This also has the additional benefit that management can then advertise they're CIS / whatever compliant to their customers.
> Get a user to build their application in a container.
> Get a user to deploy their application without you.
These two would normally be the responsibility of the CI/CD processes rather than developer preference. Do you have the authority and bandwidth to create CI/CD pipelines (be it in Jenkins or Github Actions) for their applications? Is there even a standard template for what these pipelines should look like?
> Get a user to stop logging in as root.
Change root password and take them out of sudoers.
> Get all users to stop sharing the same login and password for all servers.
Switch to SSH certificates. It's going to be an initial moment of pain getting everyone set up with private certificates, but ones it's done there wouldn't be any passwords to share.
If you want to get clether, you can even pull SSH public keys from AWS SSM, or Github, or somewhere elsewhere, so that you don't need to manage these certificates yourself.
Then add to the company IT policy that sharing private certificates is a fireable offence.
> Get a user to use configuration management rather than scp'ing config files from their laptop to the server.
Disable `scp` in the sshd_config for that user
> Get a user to stop keeping one file with all production secrets in S3, and use a secrets vault instead.
AWS has some security tooling here that might help. Though you're not going to get that for free.
> Get a user to stop using the aws root account's access keys for their application.
Just remove the keys. Ideally you'd want them to set up OAuth before hand but even a user access key would be better.
Then add hardware MFA on the root account and notification to Slack/Teams/Email you when someone does try to access it.
> Get management to give you the authority to force users to rotate their AWS access keys which are 8 years old.
AWS Security Hub is free for 30 days, so enable that and then show management the failing items. You're now presenting evidence from an authority (AWS, plus CIS, NIST, whoever if you chose to enable their frameworks too) rather than arguing about what management might perciese as your own personal opinion.
This also has the additional benefit that management can then advertise they're CIS / whatever compliant to their customers.
> Get a user to build their application in a container.
> Get a user to deploy their application without you.
These two would normally be the responsibility of the CI/CD processes rather than developer preference. Do you have the authority and bandwidth to create CI/CD pipelines (be it in Jenkins or Github Actions) for their applications? Is there even a standard template for what these pipelines should look like?