Discussion Locked

When an IT person leaves the org

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
What should an IT manager do when a systems administrator or a support person leaves their organization? What security steps do you have in place?

9 replies

by ghstinshll

unless you're going to go around renaming all kinds of accounts, restructuring the infrastructure they worked on, and all other kinds of drastic measures, I don't think there's a whole lot more than just locking out their account that you can do. Ifthey were an account administrator, there's no way to know how many admin-level accounts they may ahve given themselves a back door to. You have to believe that they're honest, and if you don't, then is it right to send out an email pertaining to keeping your eyes open for anything evident of a hacker? can this be done with pointing the finger at the ex-admin?

I'm just throwing ideas out here...

by ghstinshll

Ok, so when one of "us" leaves, we change the passwords to all major accounts, since the members of the team are able to all use these passwords, like to the backup jobs, remote console passwords, etc...

Locking their account and changing their password are a must in the least...

by lordinfidel

Each org will have a different policy.

If your in a gov or some other type of security related buis, you would probably be changing any general domain / super user type accounts.

If you are a general corp shop, and the IT mgr is leaving on good graces (no anymosity) and or he is the most top level guy and will be helping in the transistion (and you don't have a good grasp of the implications of changing the pwd/usrnme). Then I would leave it for now.

For support people, it will depend on what u/p they were privilige to.

Obviously disable their account and change their password. Also their machine should be shut down.

If they are being forced out, then definetly a u/p change is needed.

by zhang-bj

apart from blocking u/p I don't see any necessity to take other measures. a robust and efficient network infrastructure will prevent considerable unauthorized access. If the person inquestion is surely intended to do some violation, he's also at risk of being trapped.

by phillyjourno

Yeah, but not everyone's infra is as tight as
yours. Sometimes you come onto a job and
the network is put together with duct tape.
Heck, the guy leavin might be who you're
taking over for. How do you know what types of
backdoors he left for himself? Plus, all the
help desk and tech support calls he's been
on. All the user passwords he probably
knows. He could probably do some damage
with those as well. Whatta ya do about that?

by daniel.knoodle9

I really wish we could live in such a simplistic world; trust the guy who just left and "assume" your infrastructure will protect you??? What kind of naive world would that be? Any True Admin will know and understand there is always a back door just itching to be used. Especially in a multinational company where there are entry points from multiple countries. If the Admin was familiar or even helped setup these remote sites there are infinite ways to get back in. Always remember this, if it's easy for you to get in then it's just as easy for someone else with knowledge of the infrastructure!

In reality when you give someone that level of access to your systems you had better keep on his good side! Don't let them leave on a bad note or you will regret it!

by soundsolutionsinc

I have always made it a point that when a member of IT leaves, we change the system admin pw. Not just for our protection against them, but to protect someone else using that departed person's account. I also insist that it is nothing personal - just policy. When I left my last job, I forcibly had the sysadmin change the admin pw prior to me leaving (paranoid, I guess). I didn't want to be implied in anything that could have happened after I left the company.

Yes, aside from this, I also shut down their accounts, and turn off their PCs and retrieve their physical tokens for remote access. Aside from that, we are turning on auditing on all of our servers to see what accounts get created with system priviledges and by whom.

by lindadk

Just as a company has an interview to bring someone on board, there should be an exit interview. This interview should cover a checklist of items:
1 what applications did the person have access to
2 what group were they part of (as in UNIX - groupownership id GID)
3 what projects were they on that are not finished when they leave - so you can get the material to hand to another.
4 DOCUMENTATION - I can't stress enough the importance of the person documenting ALL their projects, systems they have accounts on, etc. They must let the company know this information in order to properly close out accounts, delete directories owned by them. Also, before deleting anything, make sure that they don't have applications residing within their homedirectories. Therefore, if deleted, not only is the person's account disable, but the entire application is gone.

In summary, create a boilerplate package that the manager/employee must complette before leaving the company. Then the company can be assured that all bases have been covered and the employee will not be able to access any system after leaving.

My ideas are based on working in this area and creating documents such as the ones I discuss

by urnotready

unless the person leaving is pissed. What percentage of people that are fired or layed off do you really think are going to tell you everything they touched and the status of all projects?

If I got layed off, I would tell them thatthey can hire me as a consultant to document what i was working on.

Dont like it - shouldn't have picked me to lay off. Let one of the kiss ups that you kept on try to figure out what I did.

FYI - no I did not get layed off recently, this is just an example of what to expect. ;-)

This discussion is closed to new replies.