Discussion Locked

Windows and Linux Security: A How-NOT-To

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I was reading Chad Perrin's post about Linux security vs. closed OS security, and since I've worked for years in both server environments, a couple of things struck me:

1. Linux has the advantage of the community spotting vulnerabilities and posting patches much faster than a closed OS like Windows. This is an obvious advantage in terms of quality and quantity of AVAILABLE fixes.

2. Windows updates are generally far easier to get and install (many times automatically). This provides an obvious advantage in terms of ease of staying up to date.

These two particular points are the most important, IMHO. I've been in several environments where people rely on the IDEA that Linux (and all of it's apps) is secure enough (especially with that expensive firewall). These people will only upgrade once in a while, or will use a package manager like Yum to keep their system up-to-date.

Most Linux admins can tell you that many default package managers do not have up-to-date versions of many apps, so the systems remain vulnerable while the server lies unprotected from a slew of vulnerabilities. The end result here is that if a Linux admin does not regularly keep the systems up-to-date, then it's a time bomb.

Anyone can look at the latest Changelog for a Linux app, see that the latest version fixed a vulnerability that could give attackers privileged access, start looking for servers that have not been patched yet, and take them over.

While Windows may be slower to patch holes, the process is so much easier that it often becomes automated by patch management software.

3. Someone pointed out that the most secure PC is the one disconnected from the network. The safest, greenest car is also the one that is never driven, but that's not an option for most people.

4. A properly-configured firewall and NAT can eliminate a LOT of security woes. Patching that database server may not be as big of a concern if it is located on a part of the network that is not directly accessible from the outside.

All this said, I run Linux (CentOS or Fedora) servers whenever I can, because I believe that the true difference in operating systems is in performance. There's simply no way for an operating system with a large GUI overhead to outperform a properly-tuned text-based system when using the same hardware. But that's an expanded topic for another time.

3 replies

by neon samurai

"
Anyone can look at the latest Changelog for a Linux app, see that the latest version fixed a vulnerability that could give attackers privileged access, start looking for servers that have not been patched yet, and take them over.
"

Sure, you can read the changelogs but if your poking at Windows, you'll find issues just as easy with some of the tools available. A researcher or criminal are going to learn to use the tools well also. MS is also not going to rush to tell anyone about the issue assuming it was a researcher who reported it rather than a criminal planning to use it.

Great post though. It was just that bit there which smelled of obscurity. Now to see how other's respond.

by jaqui

after all, quality is not guaranteed just because of speed and quantity in patches for issues with open source.

We expect quality from the mainstreamed apps, but that is the dedicated devs for those apps that have given us that quality. submitted patches to them are not always of the highest quality, they have to test the patches before public release of them.

by neon samurai

I usualy find speed and frequency a better indication of activity too. If a project stops putting out updates, it may have only one developer on vacation but it may also have gone dormant in favour of a better solution.

I've only been stung by updates once so far though. The phpBB v3 update decided to replace phpBB v2 and teach me why automatic updates are only for desktops. v3 is a very nice update but I'd have like to config it on the dev server at leasure first rather than rush a WTF fix against the production server. Live and learn; sometimes I even learn the easy way. :)

This discussion is closed to new replies.