, 2004-02-13
Most people don't secure their computers or act in a secure manner, and the main reason is that the average user just doesn't know what to do. Here is a checklist on security for home computer users that you can share with your friends, family, churches and clubs.
Expand all |
Post comment
Addendum
2004-02-16
Dirk (4 replies)
Dirk (4 replies)
Addendum
2004-02-17
Anonymous (2 replies)
Anonymous (2 replies)
A Home User's Security Checklist for Windows
2004-02-16
David Bala?ic (2 replies)
David Bala?ic (2 replies)
A Home User's Security Checklist for Windows
2004-02-17
Anonymous (1 replies)
Anonymous (1 replies)
A Home User's Security Checklist for Windows
2004-02-18
Anonymous (1 replies)
Anonymous (1 replies)
A Home User's Security Checklist for Windows
2004-02-19
Anonymous (1 replies)
Anonymous (1 replies)
A Home User's Security Checklist for Windows
2004-02-18
Patrick Balleux (1 replies)
Patrick Balleux (1 replies)

But, it could be simplified for non-computer administrators/gurus.
For example: (Why shouldn't I run as Administrator?) is great for someone who is skeptical and wants to know why before following someone else's advice. But for the novice who is willing to believe and just needs to be told how, how about a quick cookbook approach: (How do I tell if I'm running as Administrator?) - with a short 25 words or less explanation; (How do I set up a non Administrator ID?); (How do I run as RUNAS?) - again a short explanation would be good.
Regarding (What are some rules for good passwords?), I think someone spends too much time figuring out what not to do in passwords. For example Dictionary Words, Proper Nouns, or Foreign Words, and Personal Information can be used safely if more than 1 are used combined with numbers or special characters in a unique way. These kind will only be deciphered with brute force anyway - and will be more easily remembered without having to write them down. Writing down a very complex "approved" password would be more risky.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/220/25102#25102