Discussion Locked

IT Staff Procedures

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've been asked to come up with a procedure on handling IT staff terminations. How is everyone else handling security, accounts, etc. when an IT person with access to all/most systems leaves the company?

Any thoughts, opinions, advice will be *greatly* appreciated.

Juls

7 replies

by jamesrl

Designing the process isn't hard, but making it work can be a challenge. It depends upon the size and structure of your org how detailled you need to go.

The key is to having a list of things that need to happen (delete Net IDs, lock the computer) and a list of who needs to be notified of the need to do it. The checklist needs to track that the item is done or still outstanding.

The key to this is making sure someone(in IT security if you have such a group) owns the process and follows up until completion of all events. If it is a voluntary termination - make sure you define the time at which everything happens - last day at end of day etc. If it is a termination with cause, it should happen while the exit interview takes place - but if its too difficult to get everything done, focus on access - network ID, voice mail etc.

Hope that helps.

James

by parsonsac

Whilst I agree with the first answer to your question it doesnt take into account "back door" accounts. I myself have used backdoor accounts for use when some dilbert deletes and admin account but as this account has the same priviledges as administrators it is important that these accounts are identified and locked.

If your network has remote access accounts, (through RAS for example) then the password for this access needs to be changed immediately. I suppose its all down to wether or notthe person left of their own free will, if not then for christs sake dont tell them before the accounts are locked!

by julesmn

Thanks to both for your replies. This last issue you raise is a big part of the problem, and dial-in will be a nightmare as well. In large part, because our desktops are locked down so tight, many IT staff have a large # of user passwords in addition to some of the admins.

Thanks,
Juls

by rbaniewicz

You bring up a VERY valid reason why proceedured should call for the changing of passwords every X weeks/months. And in addition to the deleting of the fired/resigned employee's domain account, the first thing I do is change the Admins password(that's probably a given...)

by petronil

if we terminate IT pros, the first thing we do is lock out all accounts of his then changing all passwords of all systems that he have access when he was still employed. Then, secondly is we traced all accounts associated with and monitors if he breaks in or not?

by Member 26344178

If said person is unaware of the termination, at what point are the lockings carried out and also who notifies who?

by pdh13009

Before you even get close to terminating any IT staff member, make sure that you have a policy in place where any automated process or services (i.e. tape backup)use "service"
accounts and that you have them all documented, including where you have to change passwords. If your IT person created your backup process using his/her account, instead of a "service" and you disable it or even delete it, well you won't have much on your next backup will you.

Remote access is this biggest issue. So limiting the number of access points within the company can save you from having to spend two days ensuring that all of the potential entry points have been covered. We have many people that use pcAnywhere to connect to there work PC from home. If each PC had a modem, then each one of those is a point of entry for a hacker (former empolyee or not). So we make them connect through our Winframe server instead and then run PC Anywhere from there using TCP/IP to reach their work PC. It's a few extra steps, but if you already have the server, it will save you on modems and lines; not to mention the security issues.

This discussion is closed to new replies.