Removing access immediately is important for 2 reasons. The first is obviously security. Then 2nd is figuring out what he does & making sure somebody else has that access & knowledge.
If he's still in the office & gets a call or something to fix an issue it will have to get bounced to somebody else. You'll have him available to do knowledge transfer on what he use to have access to do. If he's not in the office, but still getting paid he's still available for knowledge transfer. If he's past his 2 weeks notice, he has 0 obligation to assist you guys or provide any knowledge & training to his former employers.
Whenever I give notice I expect to loose my administrative access pretty much immediately. I've already backed up anything personal. I feel no disrespect when it happens. Seriously? Boho, you are giving me 2 weeks of paid vacation time, cry me a river. It's slightly annoying if I'm still around for those 2 weeks with no privileges to do anything, but I know exactly why they have been removed. Being ostracized is one thing (and not really kosher), but merely having admin credentials revoked should be expected.
As far as a security issue goes, any competent disgruntled sysadmin has already done the done the damage or set the logic bomb before they have given their notice. Still, better safe than sorry.
First you recommend removing his access immediately, then you concede that he'll have already done any damage he was going to do by then anyway.
That's pants-on-head retarded. Prevent the damage, or don't. Remove the access, or don't. But if you're going to do one, make sure it facilitates doing the other, otherwise you're just wasting everyone's time.
In this situation, there's no animosity (the summary already said so), so there's little to be gained by revoking access. Just let the guy ride it out, and mak
Security is already done or not when the notice goes in... but shutting off access, as the GP pointed out, is done as a simulated test environment. Basically, it's a "What would things be like if he wasn't here?" while he's still around to help out if it turns out something was missed. The alternative is assuming that everyone has a perfect memory and that all systems have been adjusted appropriately, all project migrated properly, and no further questions need to be asked (in which case, why not give hi
Removing access immediately is important for 2 reasons. The first is obviously security. Then 2nd is figuring out what he does & making sure somebody else has that access & knowledge.
Beat me to it. When I saw "finishing up projects," that immediately raised a red flag. All projects should immediately be turned over to other staff, and the short termer can watch over their shoulders and answer any questions. It may make sense to let them keep email and IM during the time, and maybe even read-only to code to help look up issues. But that's about it.
For me it's not about security of the company. It's security of the person leaving, so that they can't get blamed for breaking something during that time. But the most important thing is knowledge transfer. Two weeks is a very short time to document all the little things that were picked up during their tenure.
My biggest complaint recently has been people leaving without proper knowledge transfer. Even after I emailed managers on that point, and was told to try to stop scheduling meetings with him. "He's too busy." Sigh. Now I'm left picking up the mess he left behind.
I've never resigned from a job, though been laid off twice. Once because the company went out of business and the other because the CFO (chief finance officer) panicked when one of the major customers had not issued an RFQ (request for quote) on an expected huge project. He persuaded the CEO to order a 35% reduction in staff. Because I was in the "hand off to manufacturing" phase of the project I was working one, I was one of "unlucky" people. Anyway, we were given 2 months notice and had full access until
Money will say more in one moment than the most eloquent lover can in years.
Remove access ASAP (Score:5, Informative)
Removing access immediately is important for 2 reasons. The first is obviously security. Then 2nd is figuring out what he does & making sure somebody else has that access & knowledge.
If he's still in the office & gets a call or something to fix an issue it will have to get bounced to somebody else. You'll have him available to do knowledge transfer on what he use to have access to do. If he's not in the office, but still getting paid he's still available for knowledge transfer. If he's past his 2 weeks notice, he has 0 obligation to assist you guys or provide any knowledge & training to his former employers.
Whenever I give notice I expect to loose my administrative access pretty much immediately. I've already backed up anything personal. I feel no disrespect when it happens. Seriously? Boho, you are giving me 2 weeks of paid vacation time, cry me a river. It's slightly annoying if I'm still around for those 2 weeks with no privileges to do anything, but I know exactly why they have been removed. Being ostracized is one thing (and not really kosher), but merely having admin credentials revoked should be expected.
As far as a security issue goes, any competent disgruntled sysadmin has already done the done the damage or set the logic bomb before they have given their notice. Still, better safe than sorry.
Re: (Score:1)
First you recommend removing his access immediately, then you concede that he'll have already done any damage he was going to do by then anyway.
That's pants-on-head retarded. Prevent the damage, or don't. Remove the access, or don't. But if you're going to do one, make sure it facilitates doing the other, otherwise you're just wasting everyone's time.
In this situation, there's no animosity (the summary already said so), so there's little to be gained by revoking access. Just let the guy ride it out, and mak
Re: (Score:2)
Security is already done or not when the notice goes in... but shutting off access, as the GP pointed out, is done as a simulated test environment. Basically, it's a "What would things be like if he wasn't here?" while he's still around to help out if it turns out something was missed. The alternative is assuming that everyone has a perfect memory and that all systems have been adjusted appropriately, all project migrated properly, and no further questions need to be asked (in which case, why not give hi
Re:Remove access ASAP (Score:4, Insightful)
Removing access immediately is important for 2 reasons. The first is obviously security. Then 2nd is figuring out what he does & making sure somebody else has that access & knowledge.
Beat me to it. When I saw "finishing up projects," that immediately raised a red flag. All projects should immediately be turned over to other staff, and the short termer can watch over their shoulders and answer any questions. It may make sense to let them keep email and IM during the time, and maybe even read-only to code to help look up issues. But that's about it.
For me it's not about security of the company. It's security of the person leaving, so that they can't get blamed for breaking something during that time. But the most important thing is knowledge transfer. Two weeks is a very short time to document all the little things that were picked up during their tenure.
My biggest complaint recently has been people leaving without proper knowledge transfer. Even after I emailed managers on that point, and was told to try to stop scheduling meetings with him. "He's too busy." Sigh. Now I'm left picking up the mess he left behind.
Re: (Score:2)
I've never resigned from a job, though been laid off twice. Once because the company went out of business and the other because the CFO (chief finance officer) panicked when one of the major customers had not issued an RFQ (request for quote) on an expected huge project. He persuaded the CEO to order a 35% reduction in staff. Because I was in the "hand off to manufacturing" phase of the project I was working one, I was one of "unlucky" people. Anyway, we were given 2 months notice and had full access until