Firing Network Admins

New office

Last week, during our user conference, I was doing a training session, one of the many I presented, on dealing with with confidential data within our platform. One of the points I made was that, at the end of the day someone with the proper skills needed to be the administrator of that platform, and as the administrator, they would have access to anything and everything. Much like a network administrator in any business, you either had to trust that person to do the job, and obey all of the proper policies regarding confidential information, or you had to do the job yourself.

On the other hand, while you certainly have to trust, you can also verify, so I showed the class how to run an audit log, which would show you if your admin had gone into a confidential project and looked at the data. I then opined that if I were in charge of a company and saw that my admin had been accessing confidential information, I would fire them right then and there, because I could no longer trust them.

That might sound harsh but at the end of the day, the folks with admin rights have so much responsibility that having one you don’t trust, isn’t worth it.

Today, I read something that made me want to go back and amend what I said about firing them. You might also want to make double sure and disable their access immediately too!

Ricky Joe Mitchell, 35, admitted that in June 2012, shortly after he learned he was going to be fired, remotely accessed EnerVest’s computer system and reset the company’s network servers to factory settings, essentially eliminating access to all of the company’s data and applications for the eastern US operations.

Before his access to EnerVest was terminated, Mitchell went to the office after business hours, disconnected critical pieces of computer-network equipment and disabled the equipment’s cooling system. EnerVest was unable to fully communicate or conduct business operations for nearly 30 days.

The company spent hundreds of thousands of dollars trying to recover historical data from its network servers. Some data was lost forever.

Yikes…

Similar Posts

  • Computer Repair Shops are Not Safe

    I’ve written before about the IT people in your company who probably know more about you than you might think. This now extends to taking your personal devices to a repair shop. You should assume someone might be surfing through your data while working on your computer, and you should decide if you are OK with that or if the physical destruction of the device after being replaced is the safer option.

  • Ask Questions

    I actually found much to agree with in this post about job interviews today, who’s main point is The most important thing you must do in every interview is to ask great questions. The author pointed out how it’s difficult to come across as really interested and engaged when you don’t ask questions, which hurts…

  • Copying and linking

    Christine has had a rather long discussion going on over the last 2 days about pinging weblogs.com and how anyone can take that data and use it to list your blog pretty much anywhere, etc. (It’s all tied into people figuring out how they got listed in BlogShares without their knowledge and so on and…

  • |

    Linked – How To Demotivate Your Employees

    “So, what’s causing all of this demotivation and downright unhappiness? This is indeed an extremely pressing question that all top companies should be asking themselves. Here at Netguru we make identifying the causes of demotivation one of our topmost considerations, and we’re happy to pass on what we’ve learned.” I’ve seen all of these at…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)