Says computer health should be treated like human health
It in a recent chit-chat in the recent RSA security conference, Microsoft corp's Vice President of Trustworthy Computing, Scott Charney, made an interesting suggestion. Amongst many topics such as online identification, cloud computing and more, Mr. Charney suggested a shift in how the issue of computer security is looked at. Mr. Charney encouraged the audience to look at malware, viruses, botnets and the such as a "public safety issue" instead of a more private, home safety issue.
Scott Charney went on further to suggest that this sort of hypothetical computer health service could be funded from public taxation methods, such as a broadband tax. While he did not go into great detail into his ideas, we would imagine something like this would be like a publicly-funded hospital (here in Canada), where you can bring your computers that are infected, to be cleaned out. Though this service is offered through a number of private businesses everywhere, it is imagined that if the service was covered by taxes, people would bring in computers faster, leading to less spread of malware.
As Neoseeker has mentioned recently, MS spends some funds annually on hunting down virus spreaders and botnets. Their latest victory was over the Waledac botnet -- the successor to the Storm botnet.
Unsurprisingly, Microsoft's Scott Charney did not talk much about how the overwhelmingly vast majority of malware is found on Microsoft's operating systems, and not other free OS', such as the many less-popular, but far more secure, Linux based distributions.
Section: OS & Software
| · | Asus Sabertooth X79 TUF (German) |
| · | Crucial Adrenaline |
| · | Roccat Isku |
| · | Lian Li PC-TU200 |
| · | Corsair Obsidian 550D (German) |
| · | SilenX Effizio EFZ-120HA5 |
I'd just like to point out that the main reason MS OSes are targetted is because of the vastly higher usage of them, and a greater amount of highly susceptible people like parents and children. If Macs, for example, were to become the vastly used OS, any serious virus coders would go after them instead.
Though you could argue that rates of infection would still be much lower overall if Linux-spawn were the predominate OS in town, not Windows.
Windows 7 improves things somewhat, but there are they have been many holes big enough to drive ships through, over the years, in Mircosoft OS'es. Holes that took extensive time to be patched up.
I'm not saying that it would be easy to make Windows more secure, but I would argue that when it comes to security, Windows doesn't compare well to Linux, in fundamental kernel design.
With Windows, there is in-house team working on security patches. With open source software, not only are there many, many variations of Linux, which is a great counter precisely to the situation you suggest (that the more popular an OS version is, the more attackers it will have); but in addition, with open source software were the code is public, because the entire community at large is able to point out and address and fix problems in a collaborative environment, (as opposed to a more tightly-drawn proprietary one), it is more difficult for malware-makers to sneak things through security protocols, and get greater infection rates.
To be frank, I don't specialize in malware or network security, so I'm not going to say I speak as an authority on the matter, but as described is how I see the situation. I'm always open to others' points of views.
It's irrelevant that OS9 had a lot of viruses, as Windows still held a VAST majority.
kspiess,
"that if Linux and Windows operating systems had a 50/50 split of popularity, you would still find there to be about twice or triple the malware on Windows systems as Linux systems. "
I agree. As the popularities even out, the factor of ease of infection increases more and more. Which, as you said in your example, would push Windows infection count/rate higher than Linux's. However, I do not agree on all of your reasons why, assuming the user base remains the same.
On Linux, a default installation forces you to create a standard user account for your day to day tasks and disables logging in as root from a GUI (or in Ubuntu and its derivatives, the root account is disabled all together which is a dumb idea in itself). On Windows, when you create the first user account, it's given full administrative access over the system, so all you'd have to do is go into Windows Explorer, delete C:\Windows\System32, and select OK, and you've effectively destroyed your entire OS. It's not quite that simple for a Linux system unless you know the root account's password or your account was given sudo permissions.
The following is what I was going to post but opted for the simple statement instead. There more words but it still says the same thing.
[Supernova1332 reread my post, I dont think you caught it right.]
This is the pervasive theme: The most ubiquitous operating system will be the most targeted, the most targeted will have the most units appropriated by third parties. It does have a kind of simplistic appeal, but it fails under the slightest scrutiny.
If the criminals were in complete control of our computers' security then yes, the biggest numbers would see the worst security. But the criminals are not in control of our computer's security. The operating system's vendor is. It's not my fault if I press F1 and get infected, it's the vendors fault. The criminals don't make security holes, they exploit the ones put there by the company who made the operating system.
Microsoft has been fostering this belief that computer security happens after you install your operating system. One tactic to push the responsibility for security away from themselves is to offer a huge reward for virus writers. It makes them look good but it won't make your computer any safer. In contrast Google put a reward of up to $1,331 for bugs found in their software. That will make their software safer.
Microsoft recently issued a patch for 17 year old security hole in their Windows operating system. What does that tell you? That they are a conscientious company and fix holes no matter how old they are? Maybe, but it tells me that there is 17 year old code in the heart of their center piece product.
The idea that we should pay for the security disaster caused by a defective product is outlandish. That the company responsible for that defective product is the one who suggested it puts it in the realm beyond any script Hollywood could invent.
All systems are insecure. (True) Therefore, all systems are equally insecure. (NOT true)