|
I think it is time we waged our own war against these programmer terrorists. They caused untold costs with their malicious wares. We can fight them on 3 fronts. 1) As conscientious managers, we should ferret out any of our staff that may be involved in this type of terrorism. We need to monitor the work of our programmers and look for signs of physiological imbalance. If we see any signs, we should take immediate action. Any software development area that helps perpetuate viruses should be held accountable. 2) We need to work with the software suppliers such as Microsoft, to let them know when we uncover possible security breaches. I know it is great to discover a hole and spread the word to the outside world but that fame is not worth the costs to others. I hate to read email about how such-and-such discovered a way to breach security. I would much rather get a security patch from the vendor that just says "Apply this immediately." 3) I know this one is pretty far out, but considering the costs it is probably time to look, again, at network stations for the masses of our users. I know in a couple of situations where Nimda was brought in from outside the office. If our mass of users didn't have access to floppy drives, cd roms and even hard drives, the proliferation and cleaning of these viruses would be minimized.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.