Obviously we need to start looking at better PC security measures for our local hospitals. Think about it! Anytime some kid can take down an important hospital network with little more than a select number of malware-fueled attacks from infected PCs, then I believe we need to re-think network security as a whole.

Look, I am not going to point fingers (other than at the attacker of course), however this article linked above simply illustrates to me the need to make darn sure that we become a whole lot more proactive. Think I am being too demanding? Consider the fact that the attacker also nailed US Military systems during a January 2005 attack as well…

Dateline: Blaster Worm. Ah yes, remember that one? Not only did this amazingly simple to deflect worm hit my home state DMV with its full arsenal, the worm also managed to nail a few hospitals. Folks, the method to block that attack was merely using a common sense network policy. Not only was the update available from Microsoft before the worm hit, a firewall properly used would have also prevented the damage done to productivity.

To me, the lesson that we as a collective computing world don’t appear to be grasping on is to watch what we open, download and install. As for the admins out there, let’s just say that it would appear that you still might have your work cut out for you.

Do you have some horror stories with regard to network security enforcement? Email them on over, I’d love to hear about it.

Tags: hospitals, infected pcs, blaster worm, dmv