Yet another attack.
It is amazing that most businesses and government agencies base their operations on the platform of the monolopy. Not only is it easy to exploit, but its very dominance makes it the obvious target.
Sadly much of this is caused by negligence on the part of the system administrators and system architecte types (CIO offices) .. the same people seem to be getting hammered and the same people aren't keeping up with security updates - this sort of laziness has them cobbling systems together that are exploitable.
A diversity of operating systems and important programs is clearly not a panacea, but it may well be cost effective -- and in the case of defense, even more important.
---
In going through my records for 2002 I have the following results for our home non-Windows environment ...
35,026.5 system hours of availablity out of 35,040 possible (12.5 hours were for system and program upgrades, 1 hour for dealing with a failed CD drive on a laptop). Zero hours downtime for viruses, worms and other software vulnerabilities. That is better than 99.96% availability and we always had at least three of the four machines available. While it doesn't match telco specs, it seems a bit better than what I see among Windows users (corporate, school, government, home).
The number quoted above includes the introduction of a couple of digital cameras, a camcorder, a new printer and 802.11b in the house. None of these required any work - just plug it in and it works. While configuration is a slightly different issue, I am somewhat astonished that very competent computer types often find themselves struggling with a WiFi introduction or a new camera or printer. It must be a different world.
Now if our Internet connection had 99.9%+ availability (our DSL was at 98.7% for the period we had it and our new cable service is just under 98% -- why is it that home Internet connectivity is so far from the 99.999 telco levels?
12:38:00 PM 
|
