Skip to content Request a project consultation

1 minute security check · 007 security Account Management offboarding

Mail may be blocked, but server access may remain the same.

About 5 minutes to read BlueCanvas

What accounts and keys should I organize after a developer leaves the company?

Suspending one email account is not enough. The password is something that people memorize, but the SSH public key and storage distribution key are registered on the machine, so they work the same even if you change the password. There were four positions in the server that could be counted with commands (login account, SSH public key, sudo permission, database user), and eight positions that required opening the console. Before deleting, you must first check whether the account was used together.

Key takeaways

  • Even if I suspend my email account and get a laptop, Permission to access servers and management screensmay remain.
  • Passwords are memorized by people, but The SSH public key and distribution key are registered on the machine.So, even if you change your password, it will not be deleted.
  • What you want to do today is not to erase it. getting a listno see. Simply deleting the shared account may cause both deployment and backup to stop.

It looks like it's been sorted out, but there are still some open seats.

This is usually what happens when a developer leaves the company. Suspend your company email account and receive a laptop and employee ID card. What you can see has been sorted out.

What remains is the invisible side. Access rights to servers and management screenswill not be confirmed until you create a list.

Even if you change one password, the other doors remain the same.

This is because there is more than one way to access it. Each is registered in a different way, so even if you close one, the others remain.

doorWhere is it registered?When only mail stops
company mailmail service accountclosed
SSH public key~/.ssh/authorized_keysOpen as is
database usermysql.userOpen as is
repository deployment keyDeploy keyOpen as is

Passwords are something people memorizeAnd, The public key and distribution key are registered on the machine.no see. Even if you change your password, registered lines will not be deleted. Even if you remove a collaborator from the repository, the Deploy key remains separate.

Failures appear piled up and success passes by in a single line.

This connection is less noticeable. Attempts to tap any account from outside Failed password It piles up and becomes visible immediately. On the other hand, if you enter with an already registered key, Accepted publickey It passes in one line.

The record itself remains. However, if you have set a notification based on the number of failures, this line will not be triggered. And who the key belongs to is not the log. View the list of registered keys You can tell. Rather than “an alarm will not sound even if it is breached,” it is more accurate to say “it will not be triggered by notifications that only show failure.”

There are two ways to count:

When BlueCanvas checked the existence of each item in its operating assets and counted them, the positions that could remain with access rights were divided into two. Number of digits that can be counted by command on the server four places, the place where a person has to open the console eight placesIt was.

Places in the server that can be counted using commandsHow to check
server login accountgetent passwd View accounts with a login shell as
Registered SSH public key~/.ssh/authorized_keys View the lines and comments following them.
sudo permissionsgetent group sudo and /etc/sudoers.d/ View
database userSELECT user, host FROM mysql.user; View your account and access range with
Outside of the server · Place where you need to open the consoleWhy it's important
Administrator page loginIf you use CMS, you can also see the administrator level in the member table.
FTP · SFTP accountShared hosting may have separate FTP passwords and SSH passwords.
Hosting/Cloud ConsoleIt has greater privileges than the server account as it can delete servers or create new ones.
domain registrarIf this is open, the address will be transferred to another place even if you lock the server.
Storage account and deployment keyEven if you remove a collaborator, the deployment key remains separate.
Backup Storage API KeyA backup is a full copy, so one key is equivalent to the entire server.

Since the services used are different for each business, the number of positions and names will vary. This table can be viewed as a starting point when deciding “where our company should look.”

Get the list first before deleting it.

  1. Request a list of remaining accounts and access methods in the name of the person who left the company. Collect accounts, public keys, database users, console logins, and deployment keys in one place.
  2. Before deleting, check if it is an account you used together. Simply deleting the shared account may cause both deployment and backup to stop. First check to see if cron and deployment scripts are using that account.
  3. The key distinguishes between erasing and issuing a new one. Delete only that person's key, and create a new key that was used together and replace it. If they are discarded all at once, normal service will stop.

If you are curious about the record of the person knocking on the outside, If the administrator address is /admin, how many times will it be attacked per day?You can continue watching. You can also entrust us with organizing the list and monitoring it afterwards.

The checklist, access method table, and log that appear in the text and video are reproduction screens and do not transfer actual account names or keys.

Full video subtitles (6 scenes)

I blocked email, but what about server access?

Emails from former employees have been blocked, but what about accessing the server? There is more than one way to access it.

I think it's all sorted out.

When a developer leaves, their email account is suspended and they also receive a laptop. However, the server connection may remain the same.

There are multiple doors

Even if you change your password, the registered public key will remain open. Database users and deployment keys also remain separate.

Failures pile up and success passes by

Attempts to knock from outside are counted as failures, but if you enter with a registered key, it is recorded as a normal connection.

Inside and outside the server

There are places where you can count with commands, and there are places where people have to go into the console and look at them.

Start from the list before erasing

First, get the remaining list under the name of the person who left the company, and check whether the account was used together before deleting it. There is a difference between deleting a key and issuing a new one.

Frequently Asked Questions

What accounts and keys should I organize after a developer leaves the company?

Suspending one email account is not enough. Inside the server, you need to see the login account, registered SSH public key, sudo permission, and database user, and outside the server, you need to see the administrator page, FTP/SFTP account, hosting and cloud console, domain registrar, storage account and distribution key, and backup storage API key. The first four can be counted with commands, and the last six can only be confirmed when a person opens the console.

Can’t I just change my password?

It doesn't work. The password is something that a person memorizes, but the SSH public key and storage distribution key are registered on the machine, so even if you change the password, the lines still work. Database users are also separate credentials and must be organized separately.

If I enter with the remaining key, won't it be logged?

It remains. However, it is recorded as a normal connection, not a failure. If you set a notification based on the number of failures, that line will not be notified, and you can find out whose key belongs by looking at the registered key list, not the log.

Can I immediately delete the account and key I found?

Order is required. Before deleting, you should check whether the account or key is being used elsewhere. If you simply delete the shared account, cron, deployment, and backup may stop. It is safer to delete only that person's key and create a new key that was used together and replace it. Do not dispose of them all at once.

We go through the list together, and then we watch.

Seats outside the server are not counted by command, so a person has to go in and check each console. BlueCanvas' website and server control organizes the list of accounts and keys, and even after organizing them, it constantly monitors connections and abnormal signs.

Take a look at website/server control

Other short form insights

See all short form insights→