Surprise, Windows Listed as Most Secure OS
david_g17 writes "According to a Symantec study reported by Information Week, Microsoft has the most secure operating system amongst its commercial competitors. The report only covered the last 6 months of vulnerabilities and patch releases, but the results place Microsoft operating systems above Mac OS X and Red Hat. According to the article, 'The report found that Microsoft Windows had the fewest number of patches and the shortest average patch development time of the five operating systems it monitored in the last six months of 2006.' The article continues to mention the metrics used in the study (quantity and severity of vulnerabilities as well as the amount of time one must wait for the patch to be released)."
The article also notes (which the blurb does not) that Microsoft had the most critical or severe class of bugs, even by their own measurement standard. So yes, Microsoft has less fewer bugs (according to the article), but doesn't the severity of the bugs count for anything? Statements like these are why I don't use Symantec products on any of my Windows machines.
...someone will tag the story with "defectivebydesign" and someone else will tag it with "no".
And you should have added "Those of us who think there is room in the world for both Windows, OSX and Linux will remain on the sidelines while another round of the holy wars is inconclusively decided."
I am rather looking forward to the comments from Apple users, though, and particularly whether they can best their own record for self-righteous indignation and incredulity.
Read Pynchon.
Don't go around calling "3rd grade" if you're just going to summarize a summary. RTFA already.
Here, this will help:
"The report found that Microsoft (Quote) Windows had the fewest number of patches and the shortest average patch development time of the five operating systems it monitored in the last six months of 2006.
During this period, 39 vulnerabilities, 12 of which were ranked high priority or severe, were found in Microsoft Windows and the company took an average of 21 days to fix them. It's an increase of the 22 vulnerabilities and 13-day turnaround time for the first half of 2006 but still bested the competition handily.
Red Hat Linux was the next-best performer, requiring an average of 58 days to address a total of 208 vulnerabilities. However, this was a significant increase in both problems and fix time over the first half of 2006, when there were 42 vulnerabilities in Red Hat and the average turnaround was 13 days.
The one bright spot in all of this is that of the 208 Red Hat vulnerabilities, the most of the top five operating systems, only two were considered high severity, 130 were medium severity, and 76 were considered low.
Then there's Mac OS X. Despite the latest TV ads ridiculing the security in Vista with a Matrix-like Agent playing the UAC in Vista, Apple (Quote) has nothing to brag about. Symantec found 43 vulnerabilities in Mac OS X and a 66 day turnaround on fixes. Fortunately, only one was high priority.
Like the others, this is also an increase over the first half of the year. For the first half of 2006, 21 vulnerabilities were found in Mac OS X and Apple took on average 37 days to fix them. "
It's probably a device driver issue. A bad kernel module will cause almost exactly the same error on Linux, only they call it a kernel panic instead of BSOD and write "sleeping function called from invalid context" instead of "IRQ_NOT_LESS_OR_EQUAL."
You forgot one important group (you insensitive clod!). The sensible crowd who simply dismiss the article as hot air from a group of people who have the worst security track record of their industry in the past 5 years. I mean seriously, it's pretty bad when the antivirus software starts getting hit with viruses that would otherwise be ineffective against a system. I wouldn't trust Symantec/Norton with anything more important then a string, much less consider them an "authority" on anything security related. And no, I don't use a Mac.
What a pointless comparison. All that we see is that Windows has finally caught up with other Desktop OSs in security. Desktop systems are insecure, period, so who really cares about which one is more secure. I see that there's no BSD in the list, not a single IBM OS, VMS, or any other Mainframe OS. This report completely fails to illustrate any useful information. Insecure machines can be protected with firewalls which run secure OSs, none of which were in this list (OpenBSD, anyone?). About all that can be said is that Windows has finally found a way to protect itself from the meddling of idiots, at the cost of the most annoying security system ever invented. All that, and I still doubt that any sort of stability could be achieved on a network running these three OSs exclusively, without the protection of at least one OS not in this report.
"Please describe the scientific nature of the 'whammy'" - Agent Scully
And of course:
As with previous periods, Microsoft Windows was the operating system that had the most vulnerabilities with associated exploit code and exploit activity in the wild. This may have pressured Microsoft to develop and issue patches more quickly than other vendors. Another pressure that may have influenced Microsoft's relatively short patch development time is the development of unofficial patches by third- parties in response to high-profile vulnerabilities.As always, the most secure computer is the one that is turned off, and unplugged from the network.
No security model is perfect, but I'd take any *nix for a web facing server any day.
yawn. more FUD. Have you tried Vista recently (the 'current' windows version after all). It downloads updates from the web at install time while blocking all inbound connection attempts. so, how many linux machines get "pwned" during install. lol.
Well... I think you should talk to that norwegian bank wich was down for a week (11,000 PC's and 1,000+ servers) a couple weeks ago about how secure Windows is... so no, not really "All quiet".
Vista has not been out for six months (Enterprise relese was in November, commercial release was in January) so I can't really use that info for anything... "We got the most secure system... except... it is not released yet..." geee...
...and the fact that the upgrade rate to Vista are somewhere between 30% and 50% of what Microsoft estimated is also helping the statistic.
I have run NT4 and W2K for years without problems... and without reinstalling. It is possible, you just need to know what you are doing... and how to protect your system. Wait until Joe Sixpack & other lusers start to use Vista and then we will see how invincible it is.
...and btw. I do belive Vista is the most secure Windows desktop to date... but that doesn't really say very much does it ?
No open ports on an OS X install, so it's not a problem. When I got my Mac, first thing I did was port scan it, there was squat open.
Then I noticed the firewall wasn't even on by default at that point.
The audit trail for this year's award for Best Distorting Headline:
However, that same section concludes "The risk of exploitation in the wild is a major driving force in the development of patches. As with previous periods, Microsoft Windows was the operating system that had the most vulnerabilities with associated exploit code and exploit activity in the wild (emphasis mine). This may have
I must be bored... a handy reference card:
"Mindless dribble" = "Mindless drivel", people. please. I see this so often and it grieveth me so.
-and, from previous Slashdot discussions...
"a mute point" = "a moot point"
and my absolute favorite...
"for all intensive purposes" (aaargh!) = "for all intents and purposes"
ok? fixed? I can go back to work now?
'This writing business. Pencils and what-not. Over-rated if you ask me. Silly stuff. Nothing in it' - Eeyore
no with C writing bad code is the default mode, pointer aritmetic and standard apis like prinf require extreme care to avoid writing insecure code.
o l_Cat_incident_report for more info)
secure programming in general is very hard though some languages make it harder than others. Secure programming requires carefull consideration of many issues some of which span accross the application. It also requires good documentation (how should things be quoted at this interface? is the creator of this data trustworthy or should the data be treated as potentially malicious and so on).
php does have some big issues though, newbie attractiveness is one, register_globals was another (thankfully disabled by default nowadays), another less known one involves the normal way (or at least one of the normal ways) of getting headers doing some bogus merging and hence allowing breakage of the x-forwarded-for system (which is used by sites that use reverse proxies to store the real ip of a request). (see http://en.wikipedia.org/wiki/User:Brion_VIBBER/Co
note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
All ports are closed when you fire up Windows Server 2k3 (with service pact) the first time also.
So, before we start trashing a href="http://Symantec.com">Symantec... Has anyone actually read the threat report? I didn't see anywhere that they ranked the Operating Systems in order of Most to Least secure. Also, the report makes no claim that Windows is the most secure. The Article by Internetnews says that, not Symantec. I mean, if I'm wrong, please point out where it says this in the actual report.
If I make a report that says 5000 people die in swimming pools every year, and 100 people die from base jumping, that doesn't mean I am saying that swimming is more dangerous than base jumping. If internetnews comes along and says that, well, that's their misguided interpretation.
The report gives the facts. The article takes the facts and manipulates them to say something that isn't implied. Only an idiot would make those conclusions.
A more accurate measurement might be: average time to system compromise / number of attacks.
Any real world test would be better than this silly patch counting, but the number usually reported is time to ownership. People don't really care about how many attempts it takes to break a system as much as they care about how often they need to do things. It might take an attacker 100,000 tries to brute force a password, what matters is how long it took. The trick is to make sure your network looks like a typical network and to describe those conditions so others can compare.
The usual result of tests like that is that Windoze machines are taken down in as little as four minutes with a half life of 12 minutes. Red Hat, out of the box, takes three or four months.
The Honeynet Project has all sorts of studies to further enlighten you. The bottom line is the result: More than 25% of Windoze computers are part of a bot net that's screwing everyone. It happens faster than you can download patches that won't really do you any good anyway.
Friends don't help friends install M$ junk.
This is simply not true. If your Windows 2003 machine is on any sort of network, NetBIOS is enabled if you select the default settings.
While I agree for the most part, the report that the summary doesn't reference is actually pretty good. I know, because I was 1/6 of the people who wrote it. And we have nothing to do whatsoever with the people who write the antivirus stuff, we aren't even in the same country.
This article is purely about medium- or high-impact vulnerabilities in the OS or software that comes with the OS that were patched. Unfortunately for Linux, that means almost everything.
You can read the full report here. That's a much better source than the news.
http://www.skullsecurity.org/blog/
- created an anti-virus signature that filled up your hard drive with DIR000?? folders
- has such tenacious application installs it usually takes a reformat to get them removed
- recognizes other anti-virus applications as virus activity
- purchased Ghost a few years ago and has yet to move it forward AT ALL.
- purchased Veritas last year (maybe 2) and has nearly halted all progress on that product.
Yeah, Symantec knows what it's doing.
Basically Microsoft decided to build NT as an open system (meaning standards-compliance especially with the standards of the Open Group). Some of the standards (POSIX, for example) were only barely usable, while others (DCE/RPE) became the basis for everything. At the same time, Windows use Kerberos on Domains by default, so they never implemented the security part of the spec.
DCE/RPC underlies all DCOM calls. And OLE is built on DCOM. Note that this means that you cannot turn this network service off. If it breaks, so do all manner of other things (like, for example, parts of the control panel, the clipboard, and the like). So essentially everything in Windows goes through a message bus with inadequate security.
Firewalls only buy you so much when you are up against this.
LedgerSMB: Open source Accounting/ERP