#25256
In this article, I’ll discuss how to create a strong password, and how to keep track of all your strong passwords, if you have a definite need to keep more than a couple. Don't bother creating and remembering strong passwords for low value systems, and certainly don’t use the same passwords for low value systems that you use in high value systems.
Locke, John. Free Software Magazine (2005). Articles>Software>Security
#32591
Malware: Whether on the Desktop or the Web, It’s a Perception Thing
In this column, I’ll explore the user experience of malicious software, or malware. My position is that, like many qualitative attributes, malware is in the eye of the beholder. And, I’ll suggest a method that product or service developers can use to assess the risk that their users, the media, or the market at large might perceive their offerings as malware.
Sherman, Paul J. UXmatters (2008). Articles>Software>Security
#32789
The History of Attachment Security in Outlook, Part 1
A partial history of why Outlook has so, so many viruses communicated using it, and how people at Microsoft thought to try and stop it. A study of why minor patches can't repair major architecture issues.
Lemson, K.C. KC on Exchange and Outlook (2008). Articles>Software>Email>Security
#32791
Configuring Information Rights Management for Messaging in Outlook 2003
Information Rights Management (IRM), a new feature in Microsoft® Office 2003, can help prevent sensitive information from being distributed to or read by people who do not have permission to access the content. In Microsoft Office Outlook® 2003, users can create and send e-mail messages with restricted permission to help prevent messages from being forwarded, printed, or copied and pasted. Microsoft Office 2003 documents, workbooks, and presentations that are attached to messages with restricted permission are automatically restricted as well.
