<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rossander's Security Reader &#187; Passwords</title>
	<atom:link href="http://rossander.org/infosec/category/passwords/feed/" rel="self" type="application/rss+xml" />
	<link>http://rossander.org/infosec</link>
	<description>an Information Security blog for the rest of us</description>
	<lastBuildDate>Tue, 15 May 2012 11:40:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Password joke</title>
		<link>http://rossander.org/infosec/2012/03/passwordjok/</link>
		<comments>http://rossander.org/infosec/2012/03/passwordjok/#comments</comments>
		<pubDate>Thu, 08 Mar 2012 14:20:23 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=734</guid>
		<description><![CDATA[During a recent password audit by a company, they found that one employee was using the following password: &#8220;MickeyMinniePlutoHueyLouieDeweyDonaldGoofySacramento&#8221; When asked why she had such a long password, she rolled her eyes and said: &#8220;Hello! It has to be at least 8 characters long and include at least one capital.&#8221; Sounds like a pretty good [...]]]></description>
			<content:encoded><![CDATA[<p><i>During a recent password audit by a company, they found that one employee was using the following password:</i></p>
<blockquote><p><i>&#8220;MickeyMinniePlutoHueyLouieDeweyDonaldGoofySacramento&#8221;</i></p></blockquote>
<p><i>When asked why she had such a long password, she rolled her eyes and said: &#8220;Hello! It has to be at least 8 characters long and include at least one capital.&#8221;</i></p>
<p>Sounds like a pretty good password to me.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2012/03/passwordjok/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Are passwords still viable?</title>
		<link>http://rossander.org/infosec/2010/02/are-passwords-still-viable/</link>
		<comments>http://rossander.org/infosec/2010/02/are-passwords-still-viable/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 14:19:40 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=563</guid>
		<description><![CDATA[Passwords are the least bad security option we have today.]]></description>
			<content:encoded><![CDATA[<p> How many different passwords do you have?  Add up all the ones on your work computer, your bank account, 401(k), personal email account, amazon, google, ebay, twitter, facebook, linkedin, wikipedia, professional organizations, other shopping sites&#8230;  The list goes on and on.</p>
<p> Each password has to be strong enough to protect the information behind it.  Of course, knowing that we are all basically lazy (and that they will be held responsible if the account is hacked), the companies hosting these services require &#8220;strong&#8221; passwords &#8211; numbers, punctuation, no duplication, etc.  And without universal standards, we end up with a hodge-podge of passwords that are impossible to keep straight.</p>
<p> One answer is a &#8220;password management&#8221; program, often built right into your web browser.  These programs remember your logins and passwords for you and automatically fill them in as soon as you go to the page.  There are several problems with them, though.</p>
<ol>
<li> When your computer gets stolen, you lose <i>all</i> your passwords.</li>
<li> If the <a href=http://rossander.org/infosec/2006/11/stored-password-vulnerability/>password manager gets hacked</a>, you again lose everything all at once.</li>
<li> The passwords are only available while you&#8217;re working on that one computer.  You&#8217;re out of luck if you need to check your account from your mother-in-law&#8217;s.</li>
<li> And, of course, these don&#8217;t do anything for the passwords you need to track that aren&#8217;t associated with web pages.</li>
</ol>
<p> A perhaps-better answer is a single-signon service.  In this model, you create one account with a widely accepted and trusted service who then authenticates you to the merchants.  The <a href=http://openid.net/>Open ID Foundation</a> is probably the best known, accepted by about 9 million websites including Google and Yahoo.  This still leaves all your eggs in one basket but at least the basket is not in your easily-stealable laptop.  On the other hand, if any one of those 9 million websites gets hacked, the thief might then be able to forge your credentials on the other sites.  I&#8217;d trust their service for accounts I don&#8217;t care much about (google, email, shopping sites, etc) but not yet for my bank account.</p>
<p> Several academics are experimenting with using your cell phone as your password manager.  It&#8217;s an interesting idea since we are so very attached to them.  But we also lose them at an incredible rate.  And if you think you get resistence about your computer passwords, try requiring a strong password on a phone.</p>
<p> Biometrics?  There are some interesting new ideas about facial recognition using the builtin webcam of many modern laptops and others that track things like your typing patterns.  None are ready for prime time yet.</p>
<p> All told, I think we&#8217;re still in a bad place.  Passwords are the least unworkable answer we have today.  Try to pick <a href=http://rossander.org/infosec/2010/01/resolve-to-make-stronger-passwords-in-2010/>strong passwords</a>, use a pattern that lets you <a href=http://rossander.org/infosec/2008/02/managing-multiple-passwords/>modify a core password</a> according to the site you&#8217;re visiting, change the important ones regularly and <a href=http://rossander.org/infosec/2008/01/never-share-your-password/><b>never, never, never</b></a> share your password.  If you must write them down, keep them in a dedicated and highly secure application like the old Blackberry password vault.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2010/02/are-passwords-still-viable/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolve to make stronger passwords in 2010</title>
		<link>http://rossander.org/infosec/2010/01/resolve-to-make-stronger-passwords-in-2010/</link>
		<comments>http://rossander.org/infosec/2010/01/resolve-to-make-stronger-passwords-in-2010/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 20:59:54 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=550</guid>
		<description><![CDATA[Resolve to pick stronger passwords.  Use pass-phrases, use variant rules and never share your password.]]></description>
			<content:encoded><![CDATA[<p>Happy New Year, all.  I hope you had a wonderful and safe holiday.  It&#8217;s a brand new year &#8211; time to make resolutions to do better and be better people.</p>
<p>One resolution that we&#8217;ve talked about before is the need to make better, stronger passwords to keep your identity and your customers&#8217; informations secure.  Americans still have a nasty habit of picking passwords from the dictionary.  When the system requires numbers or extra characters, we tend to add them to the end.  Hackers know this and exploit the pattern when they build programs to break your password.  Here are a few suggestions to make their lives harder (without making your passwords so impossible to remember that you write them down).  None of these suggestions are new but hopefully this is a useful reminder.</p>
<ol>
<li> Pick a <a href=http://rossander.org/infosec/2008/01/resolve-to-make-stronger-passwords-in-2008/>pass <b>phrase</b></a>, not a pass<b>word</b>.  A good hacker can test your password against every word in the dictionary in something under 30 sec.  Testing every possible combination of 7 random characters takes not that much longer.  A five word passphrase, on the other hand, can not be brute-forced using current computers in the time remaining in the life of the universe.  And because of how our brains are wired, phrases are much easier to remember than strings of characters.</li>
<li> Make each password a unique variant using some personal rule about the site that you&#8217;re logging into.  That way, you won&#8217;t lose everything just because the hacker cracks one site but you can still keep the number of things you must memorize to a minimum.  <a href=http://rossander.org/infosec/2008/02/managing-multiple-passwords/>Here</a> is a link to one technique.</li>
<li> Never share your password.  Not to your boss, your co-workers, your spouse, no one.  Nobody should know your password except you.  (The only exception I allow is that parents should insist on a copy of all passwords used by their underage children.  Keep it safe, though.)</li>
<li> Make sure you&#8217;ve changed the <a href=http://rossander.org/infosec/2007/04/drive-by-router-vulnerability/>default password</a> on accessories like your router.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2010/01/resolve-to-make-stronger-passwords-in-2010/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Anyone can get hacked</title>
		<link>http://rossander.org/infosec/2009/11/anyone-can-get-hacked/</link>
		<comments>http://rossander.org/infosec/2009/11/anyone-can-get-hacked/#comments</comments>
		<pubDate>Tue, 10 Nov 2009 00:48:17 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Malware]]></category>
		<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=529</guid>
		<description><![CDATA[A case study of a vandalism attack on a website.]]></description>
			<content:encoded><![CDATA[<p> Sorry I haven&#8217;t posted in a while but it&#8217;s been an interesting few weeks.  If you&#8217;d looked at this site on the morning of 6 October, you would have seen a very different page &#8211; black background, yellow arabic writing and some very disturbing pictures.  The vandal replaced the front page of our local beekeepers&#8217; website with very similar content.  It was a rude surprise, especially so early in the day.</p>
<p> Some background &#8211; I maintain the beekeepers&#8217; website for them and host both that site and this one through a third-party provider.  And while I do all of the writing for the infosec blog, I have a couple of other beekeepers who were helping to maintain the beekeepers&#8217; site.  It&#8217;s all volunteer work and I&#8217;m so glad for any help I can get that it&#8217;s hard to impose a lot of strict standards or hurdles.  Besides, who cares about hacking a beekeeper club&#8217;s website?</p>
<p> Apparently lots of people.</p>
<p>  It&#8217;s unlikely that we will be able to prove exactly how the hacker got in but it was almost certainly a scripted attack &#8211; a robot run by a hacker against anything he/she could find vulnerable &#8211; not a targeted attack.  (For example, the hacker vandalized only pages titled <tt>index.htm</tt>, the standard name for a site&#8217;s home page, and none of the pages which had human-created names.  Any targeted attack would have overwritten the other pages as well.  Not only would it be more pages hacked but the vandalism might go unnoticed longer.)  Our best guess is that the hacker go in because we weren&#8217;t careful enough about passwords.  One of my authors had a password the same as his username.  Even a kiddy-script can test for passwords that easy.</p>
<p> <b>Lessons Learned:</b></p>
<ul>
<li> Any site is vulnerable even if you don&#8217;t think that anyone would bother with little old me.</li>
<li> Passwords are important, even when you think they aren&#8217;t.</li>
<li> Volunteer time is valuable but only if it&#8217;s the right volunteer.  Even if his/her heart&#8217;s in the right place, sometimes that time is more expensive than it&#8217;s worth.</li>
<li> Internal segmentation would have limited the damage.  Merged accounts makes it easier to manage the domains but separate accounts would have kept the hacker from &#8220;promoting&#8221; himself across to the other accounts so easily.</li>
<li> Monitoring is a good thing.  In my case, it was dumb luck.  My wife has the site as one of her home pages and noticed it as soon she logged on in the morning.</li>
<li> Good backups make repairing the damage easy.  My backups are automatically managed through third-party host and they do an excellent job.  Once we discovered the vandalism and collected the evidence, the act of repairing the vandalism took mere minutes.  I wish I could take credit for it but I got lucky and picked a good vendor.</li>
</ul>
<p> Anyone can get hacked.  Do what you can to minimize your chances, discover it quickly and plan so the costs to repair are low.  I can&#8217;t say that I&#8217;m proud of this post but I do hope that you can learn from my mistakes.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/11/anyone-can-get-hacked/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adobe weakens passwords – sort of</title>
		<link>http://rossander.org/infosec/2009/01/adobe-weakens-passwords-%e2%80%93-sort-of/</link>
		<comments>http://rossander.org/infosec/2009/01/adobe-weakens-passwords-%e2%80%93-sort-of/#comments</comments>
		<pubDate>Tue, 27 Jan 2009 03:37:46 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=381</guid>
		<description><![CDATA[If you use password-protected Adobe files (pdf) to pass your data securely, their recent change to the software may mean you have to change how you pick your passwords.]]></description>
			<content:encoded><![CDATA[<p>There was a story last month that Adobe&#8217;s latest release (Acrobat 9) actually weakened the strength of the algorithm they use for passwords that protect PDF documents.  If you&#8217;re using password-protected PDFs as a way to send confidential information to your customers or business partners, does this mean that you can no longer trust the protection?</p>
<p>There is a lot of confusion because at the same time, Adobe increased the encryption from 128-bit to 256-bit.  More is better, right?  All things being equal, that&#8217;s usually true.  In this case though, they also changed the way the encryption works.  The net result is that the password is now crackable about 100 times faster than with the older Adobe versions.</p>
<p>If you are using weak passwords, this change matters a lot.  Passwords that used to take 3 months to crack will now be breakable in a little over a day.  If you&#8217;re still using single english words for your password, your protection is weak at best.  A brute-force attack (where the hacker tests every word in the dictionary against your document) will break a weak password in minutes.  On the other hand, if you&#8217;re picking strong <a href=http://rossander.org/infosec/?p=54>pass-phrases</a> – whole sentences from a favorite book or song – and if your phrase includes upper case, lower case, numbers <i><u>and</u></i> special characters, your cracktime is probably still measured in millennia.  I tend to like sentences from children&#8217;s counting books such as &#8220;On Monday, he ate thru 1 apple.&#8221; from <i>The Very Hungry Caterpillar</i>.  Not only does it have all four character classes, but I&#8217;ve read that book far too many times – there&#8217;s no chance that I&#8217;ll ever forget that pass-phrase.  Combine that phrase with the <a href=http://rossander.org/infosec/?p=47>prefix trick</a> for managing multiple passwords and your password will outlast a thousand hackers.</p>
<p>The one unambiguously good thing about this change is that Adobe got rid of the 32 character limit.  You can now type as much as you want for your pass-phrase (up to 127 characters – and even I&#8217;ve never hit that limit).  If you take advantage of that increase, the change to version 9 is a net security benefit even with the change to the algorithm.  You can read more at <a href=http://www.pcworld.com/article/155012/article.html?tk=nl_dnxnws>PCWorld.com</a> or on Adobe&#8217;s own <a href=http://blogs.adobe.com/security/2008/12/acrobat_9_and_password_encrypt.html>security blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2009/01/adobe-weakens-passwords-%e2%80%93-sort-of/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stolen laptops</title>
		<link>http://rossander.org/infosec/2008/11/stolen-laptops/</link>
		<comments>http://rossander.org/infosec/2008/11/stolen-laptops/#comments</comments>
		<pubDate>Mon, 03 Nov 2008 22:37:07 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Cybercrime Trends]]></category>
		<category><![CDATA[Passwords]]></category>
		<category><![CDATA[Physical Security]]></category>
		<category><![CDATA[breach disclosure]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[laptop]]></category>
		<category><![CDATA[strong password]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=13</guid>
		<description><![CDATA[Laptops remain high-risk, high-theft devices.  Make sure your people know how to protect them appropriately.
]]></description>
			<content:encoded><![CDATA[<p>Law enforcement agencies are reporting a recent uptick in the number of lost or stolen laptop computers. It&#8217;s not clear yet whether this is a random fluctuation, a consequence of the troubled economy or something else but it is a disturbing trend.</p>
<p>Laptop computers represent one of most significant information risks for any company because of the sheer volume of confidential information that they can hold. Worse, even if you don&#8217;t think you&#8217;ve ever saved a confidential document onto your computer, the computer will almost certainly have the access credentials needed to access information that is centrally held. One stolen laptop can put <em>all</em> of your data at risk. In those situations, the state-level breach disclosure laws put the burden on the breached company to show that their information was not compromised. When in doubt, the company must disclose. So unless you know positively what information got stolen, you might have to assume that all of it was and notify everyone in your database. Thousands of notifications, leading to lawsuits, wasted time, panicked customers and, most seriously, a loss of trust with your customers.</p>
<p>For most companies, there are two thin lines that protect your customer information.</p>
<p>One is each individual employee&#8217;s practice of protecting the computer itself. The vast majority of laptop thefts are crimes of opportunity so don&#8217;t give the criminal the opportunity. Have a policy that requires your staff to keep their laptops locked up at night. If leaving the computer at the office, put it in a desk drawer or cabinet &#8211; out of sight, out of mind. Don&#8217;t assume that the door lock will be sufficient to keep the thieves out. (See this <a href="http://www.sptimes.com/2007/10/28/Business/Here_s_how_a_slick_la.shtml">Times article</a> for an example of how easily a professional thief can impersonate his/her way into a supposedly secured office.) If your staff are taking the computer home, make sure they know to either bring it in with them or lock the computer in the trunk if they have to stop on the way. Never let the computers be left exposed.</p>
<p>The second line of defense is encryption. Scrambling your data can provide protection in case the unthinkable happens. That encryption, however, is no stronger than the key used to unlock it. For many companies, the encryption is based on a password (often the same password used to log onto the computer in the morning). Always pick a <a href=http://rossander.org/infosec/?p=54>strong password</a>. Don&#8217;t just pick a word, capitalize the first letter and add some numbers at the end. This is a natural tendency for english-speakers and the hackers know it. They optimize their cracking routines to break passwords in this pattern and will crack them in mere minutes. Use whole sentences instead. Whole sentences are easy to remember but far harder to break.</p>
<p>And never, never, never write down your password and leave it with the device you are trying to protect. That would be like buying a $3000 security door for your home, then leaving the key in the lock. You&#8217;d never be that careless at home. Don&#8217;t let people be careless at work, either.</p>
<p>If you have a laptop, protect it. Even one loss is too many. </p>
<p><b>Credit report reminder</b></p>
<p>For those of us on the &quot;<a href=http://rossander.org/infosec/?p=45>trimester plan</a>&quot; for reviewing our credit reports, it&#8217;s time to ask for your free copy of your credit report from the next agency.</p>
<div align=right><small><i>From <a href=http://infosec.westfieldinsurance.com/2008/11/stolen-laptops.html>westfieldinsurance.com</a></i></small></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2008/11/stolen-laptops/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing multiple passwords</title>
		<link>http://rossander.org/infosec/2008/02/managing-multiple-passwords/</link>
		<comments>http://rossander.org/infosec/2008/02/managing-multiple-passwords/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 07:00:00 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=47</guid>
		<description><![CDATA[These days, keeping all your passwords straight can be an almost impossible task. Every website and application needs a password. Do you pick the same password and use it everywhere or do you write them down? If you use the same password, you&#8217;ll lose them all as soon as any one of those systems gets [...]]]></description>
			<content:encoded><![CDATA[<p>These days, keeping all your passwords straight can be an almost impossible task. Every website and application needs a password. Do you pick the same password and use it everywhere or do you write them down? If you use the same password, you&#8217;ll lose them all as soon as any one of those systems gets compromised. But if you write them down, you lose them all when your sticky-note gets lost or stolen.</p>
<p>Here&#8217;s a trick for making semi-customized passwords that will be easy to memorize but still unique to each site.</p>
<p>Pick a &quot;static&quot; password. (For this example, I&#8217;ll use &quot;Bluebird&quot; but a <a href=http://rossander.org/infosec/?p=54>passphrase</a> is much better.) Now look at the website or application that you&#8217;re signing onto. Make up a personal rule about the website name such as:</p>
<ol>
<li>The first digit of my password will always be the second letter of the website&#8217;s name.</li>
<li>The second digit of my password will always be the number of characters in the website&#8217;s name.</li>
<li>The third digit will be a dash.</li>
</ol>
<p>The password at Amazon would be &quot;m6-Bluebird&quot; and at eBay would be &quot;b4-Bluebird&quot;. The password on your home Dell computer might be &quot;e4-Bluebird&quot;. A password in this pattern is reasonably strong because it has all four character classes (uppercase, lowercase, number, punctuation) and because it doesn&#8217;t follow the predictable tendency for English speakers to capitalize the first letter and put the number(s) at the end. Best of all, every password is different but you only have the one phrase to memorize and one rule.</p>
<p>There are a couple of limitations to this technique.</p>
<ul>
<li>You must be the only person who knows your exact rules. <strong>Do not</strong> use the exact rules above. Make your own choices about which letter, punctuation, etc.</li>
<li>Some systems won&#8217;t allow special characters (like the dash) or may have size limits on the password. Unfortunately, there&#8217;s no easy way around those problems. Make the best choice you can given the limits of the system and write down only enough to remind yourself what&#8217;s different (such as &quot;401k &#8211; no dash&quot;). If it&#8217;s an important system (like your online bank), lobby the company to allow stronger passphrases.</li>
</ul>
<div align=right><small><i>From <a href=http://infosec.westfieldinsurance.com/2008/02/managing-multip.html>westfieldinsurance.com</a></i></small></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2008/02/managing-multiple-passwords/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Never share your password</title>
		<link>http://rossander.org/infosec/2008/01/never-share-your-password/</link>
		<comments>http://rossander.org/infosec/2008/01/never-share-your-password/#comments</comments>
		<pubDate>Mon, 28 Jan 2008 07:00:00 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=51</guid>
		<description><![CDATA[As a user, you should never share your password with anyone. It is used to track who had access and made changes to specific information. You are responsible for everything done on the system using your ID and password. As a manager, you must set up the processes and procedures so that your staff and [...]]]></description>
			<content:encoded><![CDATA[<p>As a user, you should <strong>never</strong> share your password with anyone. It is used to track who had access and made changes to specific information. <strong>You</strong> are responsible for everything done on the system using your ID and password.</p>
<p>As a manager, you must set up the processes and procedures so that your staff and customers do not <em>need</em> to share their passwords. They need a simple rule that anyone asking for their password is running a con.</p>
<ul>
<li>The user&#8217;s co-workers should never have access to each others&#8217; passwords. If work needs to be shared, use shared folders or other collaboration tools that maintain tracabilty in the logs about who did what. If a co-worker needs temporary access to the user&#8217;s files (for example, if covering for someone on vacation or emergency medical leave), have IT use their administrative tools to grant the access rights under their own ID, not by compromising the ID of the person who is out of the office.</li>
<li>Not even your own IT staff should ask for a user&#8217;s password. If IT needs the password to complete a repair, the IT person should insist that the user type in the password.</li>
<li>You don&#8217;t need their password either. If you need to access their files, you should have IT set up your rights so that you can monitor their work under <em>your own</em> ID and password. No one ever wants to be in the middle of an investigation but, if you are, you really don&#8217;t want to have counter-accusations that the chain of evidence was compromised.</li>
</ul>
<p>Too many people are running phishing and other cons that try to trick people into sharing their passwords. Make it possible to say with confidence that <strong>no one</strong> at your organization will ever ask you for your password.</p>
<div align=right><small><i>From <a href=http://infosec.westfieldinsurance.com/2008/01/never-share-you.html>westfieldinsurance.com</a></i></small></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2008/01/never-share-your-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolve to make stronger passwords in 2008</title>
		<link>http://rossander.org/infosec/2008/01/resolve-to-make-stronger-passwords-in-2008/</link>
		<comments>http://rossander.org/infosec/2008/01/resolve-to-make-stronger-passwords-in-2008/#comments</comments>
		<pubDate>Mon, 07 Jan 2008 07:00:00 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=54</guid>
		<description><![CDATA[Resolve to make better passwords by picking passphrases instead.]]></description>
			<content:encoded><![CDATA[<p>According to a non-scientific survey I just conducted, the most common question this time of year is &#8220;How were your holidays?&#8221;  The second most common question is &#8220;Have you broken your New Year&#8217;s resolutions yet?&#8221;</p>
<p>Here&#8217;s a trick to help keep at least a few of those resolutions by choosing stronger passwords.  As we&#8217;ve talked about <a href=http://rossander.org/infosec/2007/01/resolve-to-pick-stronger-passwords-in-2007/>before</a>, pass<b>words</b> are fairly easy to break because most of us pick an English word, capitalize the first character and add a number at the end.  That&#8217;s a statistically common trend among English-speakers.  It meets the minimum complexity rules but will fail to a password cracking tool in 30 seconds or less.</p>
<p>If your New Year&#8217;s resolution is your passphrase, you&#8217;ll get a strong password that is hard for an outsider to break.  (Microsoft&#8217;s password rules allow up to 127 characters and permit any character on the keyboard, <b>including the spacebar</b>.  You can pick a whole sentence including spaces and punctuation for your password.)  And by typing it several times a day, well, maybe repetition will help me actually live up to the resolution.  For example, I need to eat less and exercise more.  If my password for the month is &#8220;<tt>Take the Stairs.</tt>&#8220;, I&#8217;m reminding myself several times a day that I shouldn&#8217;t be lazy – that those extra steps are good for me.</p>
<p>A couple of thoughts, though. First, don&#8217;t make your password obvious to others. If your password is &#8220;<tt>Spend more time with your Kids!</tt>&#8220;, don&#8217;t make a poster with the same phrase and hang it in your office. Second, add unusual capitalization or swap a letter for a number in the middle of the phrase. For example, &#8220;<tt>Give more time 2 Charity.</tt>&#8221; Even if someone does guess your resolution, they won&#8217;t know what little change you&#8217;ve made to the way you type it. Put together, you&#8217;ll have a strong password that&#8217;s easy to remember and might actually help you keep that resolution a little longer.</p>
<div align=right><small><i>From <a href=http://infosec.westfieldinsurance.com/2008/01/resolve-to-make.html>westfieldinsurance.com</a></i></small></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2008/01/resolve-to-make-stronger-passwords-in-2008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Password security</title>
		<link>http://rossander.org/infosec/2007/08/password-security/</link>
		<comments>http://rossander.org/infosec/2007/08/password-security/#comments</comments>
		<pubDate>Mon, 13 Aug 2007 07:00:00 +0000</pubDate>
		<dc:creator>Mike Rossander</dc:creator>
				<category><![CDATA[Passwords]]></category>

		<guid isPermaLink="false">http://rossander.org/infosec/?p=71</guid>
		<description><![CDATA[Passwords are only useful if they are kept secret. That sounds obvious but we are still finding users who tape their passwords to the computer or &#34;hide&#34; them in an unlocked desk drawer. Laptop and desktop computers represent the single greatest risk to the computer systems and customer private information of most organizations. A stolen [...]]]></description>
			<content:encoded><![CDATA[<p>Passwords are only useful if they are kept secret. That sounds obvious but we are still finding users who tape their passwords to the computer or &quot;hide&quot; them in an unlocked desk drawer.</p>
<p>Laptop and desktop computers represent the single greatest risk to the computer systems and customer private information of most organizations. A stolen or lost laptop is a gold mine for an identity thief. Laptops and desktops hold all kinds of private information (often including the access rights and certificates necessary for a hack to get onto the rest of the network).</p>
<p>In order to mitigate the risk, many organizations have encrypted their computers – scrambled the content so that, in theory, if a computer is stolen, the thief gets away with a $2000 doorstop. Unfortunately, that encryption is often completely dependent on the password. If the thief also gets away with the password, they have access to everything and all the organization&#8217;s defenses are for naught.</p>
<p>Make it very clear to your staff that <b>leaving a password unprotected is a very serious violation of your security policies</b>. If they see an unsecured password, have them report it immediately to their manager or supervisor.</p>
<div align=right><small><i>From <a href=http://infosec.westfieldinsurance.com/2007/08/password-securi.html>westfieldinsurance.com</a></i></small></div>
]]></content:encoded>
			<wfw:commentRss>http://rossander.org/infosec/2007/08/password-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

