zimv20 said:
that's a good start. for windows machines (some aren't windows-specific, i know), i recommend:
- making your daily account not have administrator access
[snip]
This is an interesting part, and speaks to one of the largest problems MS will have to fight in their uphill battle -- culture
I'm a long time unix geek, so when I installed Win2k on a home computer I automatically created two accounts, one admin, and one completely unpriviliged.
[side note -- I didn't create a "power user" because nowhere could I find a concise definition of what permissions a power user was given, so I couldn't even determine the security risks. Strike one]
I very quickly found out it is incredibly frustrating and almost impossible to run as anything other than admin (or, I presume, power user). A huge amount of sofware absolutely requires admin, for no particular purpose. Off the top of my head:
1) My HP scanner software (yup, non-admins couldn't scan)
2) Palm desktop -- now I understand why the hotsync manager has to be run as admin, but the desktop portion?!?!
3) Microsoft Word! -- admittedly it was an older version (word 98 I think), but not so old that NT4 hadn't already existed. I either had to run it as admin, or grant world write permission to my system32 directory!
4) ICQ -- yup, no IM if you're not an admin
Until MS educates their ISV's to recognize the security implicatations and build the software correctly for multi-user machines they are going to have a virus and worm problem. Heck, I even got to the point of considering saying to hell with it and just making my account an admin.
OSX, OTOH, with the "administer via sudo" concept does a pretty good job of avoiding the virus and worm issue even if your day to day account does have admin priv, and now can concentrate mainly on trojans.