Tui Itm 550 Network Administration Essay

1847 Words Dec 17th, 2011 8 Pages
ITM 550


5 June 2011

Why do companies find it necessary to distinguish between network administration and systems administration?

The first line of defense for almost every organization is typically the system administrator. This is the person that actively interacts with the company network on a daily basis, and by extension has intimate knowledge of it. So it stands to reason that this person would hopefully be the first to notice any signs of possible compromise would it not? Sadly that is often not the case. Whether it is due to a lack of IT Training, complacency, or laziness is anyone’s guess.
Several of the company networks that I have been involved with have the same story. All of them have
…show more content…
That or a box is rebuilt and the sys admin puts it back on the network with no patches, as they will install them in a second or two.
If I had a nickel...
I don’t know how many times I have heard this when the admin in charge is queried after the fact while an incident is investigated. “Geez it was only on the network for a minute or two!” No one really expects the sys admin to be a security guru but certain fundamental practices must be observed. One of those is to have all those patches on a cdrom so that the rebuilt machine can be patched offline. Much like the admin checking on a daily basis for newly released system patches. It’s just good business after all.
So to wrap up all of the above verbiage, what should one do to ensure the sys admin is staying on top of patches? Well simply put, I would have a sheet where the sys admin would need to sign off on. That person’s signature would attest to their having verified the vendor site for patches each and every day. Not only that but I would personally have them checking out the mailing lists as well on a daily basis. This would help give them situational awareness as it impacts them and their network. With that in mind if the sys admin has indeed signed off on that sheet and the company is compromised because of an old exploit then the answer is simple. You’re fired!
Many system administrators out there may find this rather harsh. The reality of it is that there is little to no accountability for system

Related Documents