{"id":7294,"date":"2006-11-13T13:12:00","date_gmt":"2006-11-13T13:12:00","guid":{"rendered":"https:\/\/www.practicallynetworked.com\/?p=7294"},"modified":"2022-11-10T13:13:48","modified_gmt":"2022-11-10T13:13:48","slug":"dont-fall-prey-to-lazy-password-practices","status":"publish","type":"post","link":"https:\/\/www.practicallynetworked.com\/dont-fall-prey-to-lazy-password-practices\/","title":{"rendered":"<strong>Don&#8217;t Fall Prey to Lazy Password Practices<\/strong>"},"content":{"rendered":"\n<p><strong>Building strong passwords helps you protect both business and personal data from unauthorized access. But passwords are meaningless if they are too simple or written down where other can access them.<\/strong><\/p>\n\n\n\n<p><strong>Ronald V. Pacchiano<\/strong><\/p>\n\n\n\n<p>Earlier this week I was at a client site setting up a PC for a new user. Everything was going fine until the system needed to be authenticated to the network. In order to accomplish this, you need to be using an account with administrative privileges. <\/p>\n\n\n\n<p>The one I was using didn&#8217;t. This meant that I would need to have the office manager handle this part of the installation for me. Unfortunately, though, when I went to get her I discovered that she was in the middle of a meeting and could not be disturbed. <\/p>\n\n\n\n<p>This meant that for the moment, there was nothing left for me to do, other than perhaps get some lunch.<\/p>\n\n\n\n<p>Just as I was getting ready to write her a note regarding my whereabouts, I noticed something attached to the base of her monitor. Can you guess what it was? That&#8217;s right: a yellow Post-it note with her password written on it. Right out in the open for anyone to see. Since her password was available, I used it to finish setting up the new PC.<\/p>\n\n\n\n<p>Despite the fact that her carelessness proved helpful for my situation, the fact remains that the password to her administrative user account was left out in the open, completely unsecured and accessible to anyone who stepped into the room \u2014 whether that be a cleaning person, a visiting guest or an employee with a grudge. No matter how you look at it, this is a very serious breach of security and has potentially disastrous ramifications.<\/p>\n\n\n\n<p>However, this scenario is not a unique one. I have seen this type of behavior displayed by employees in companies both big and small, and at various management levels. The biggest offenders are typically older office associates or absent-minded CEOs who can&#8217;t be bothered with such petty things.<\/p>\n\n\n\n<p>No matter how often I run across this, it never fails to amaze me at how careless people can be with something as important as password security. Proper password management is crucial to maintaining the security of your network. <\/p>\n\n\n\n<p>The way it works is simple, your network account provides you (and theoretically ONLY you) with the means to access confidential and potentially damaging network resources, while simultaneously denying the same access to anyone who isn&#8217;t authorized to be viewing or using them. <\/p>\n\n\n\n<p>The only thing that maintains this secured environment is the diligent protection of your user account. And the only thing protecting that is your password. This is why you need to protect your passwords, make them strong and change them frequently.<\/p>\n\n\n\n<p>In case you need a little motivation, here&#8217;s something you might not be aware of. Did you know that you are accountable for ALL activity conducted on the network with your user account? Sharing your password potentially makes you accountable for the activities of others, and in most cases, is a major violation of a company&#8217;s security policy. In some cases it can even be grounds for dismissal. Also, depending on where you work and the type of resources you have access to, a breach in network security due to your negligence could expose you to potential criminal charges as well.<\/p>\n\n\n\n<p>It&#8217;s in your best interest to change your password to one that complies with the established guidelines for strong and secure password creation and then adopt responsible practices for keeping it from falling into unauthorized hands.<\/p>\n\n\n\n<p>To that end, your password should never have any of these characteristics:<\/p>\n\n\n\n<ul>\n<li>personal data such as a child&#8217;s name, birthdays or a favorite possession<\/li>\n\n\n\n<li>use anything easily guessed, repetitive or running in sequential patterns (&#8220;111111&#8221;, &#8220;123456&#8221;, &#8220;abc123&#8221;)<\/li>\n\n\n\n<li>comprised of more than three consecutive letters from your network account<\/li>\n\n\n\n<li>be less than six characters long<\/li>\n<\/ul>\n\n\n\n<p>And, most importantly, don&#8217;t ever write down your password in an unsecured manner or share your current password (or even a previous password) with anyone. Not with your boss, not with a co-worker, not with your administrative assistant. Even your IT team would never need to ask you for your password. If needed, they could reset it.<\/p>\n\n\n\n<div style=\"height:50px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>What Makes a Password Strong<\/strong><\/p>\n\n\n\n<p>Now that we know what not to do, we have to ask the question &#8220;what constitutes a strong password?&#8221; In order to ensure maximum protection, your passwords should be at least eight characters long. Microsoft recommends at least six characters, but eight characters will be significantly harder to crack. For optimal security, they should also contain a mix of alpha-numerical characters, in both upper and lower case, as well as special characters like !#%$&amp;.<\/p>\n\n\n\n<p>Ideally, it shouldn&#8217;t even be a real word; just random characters. The more random the sequence of characters, the more secure the password will be. An example of a secure password would be something like&#8221;<strong>Hgs3@4j55nKX!s!<\/strong>&#8220;. This password is 15 characters long and contains a combination of numbers, symbols, upper and lowercase letters. Also, since it&#8217;s long and totally random, it will be far tougher for someone to hack.<\/p>\n\n\n\n<p>Regrettably, though, most users don&#8217;t conform to these guidelines. The primary reason for this is simple. A proper password is generally so complex that most people can&#8217;t remember it without writing it down. However, a strong password doesn&#8217;t have to be hard to remember though \u2014 just hard for someone else to guess. To help get you started here are some tips for constructing a strong, yet easily remembered password.<\/p>\n\n\n\n<p><strong>Numbers for letters<\/strong>: Some numbers bear a strong resemblance to letters and vice versa. For example, the number&#8221;1&#8243; looks a lot like the letter &#8220;l&#8221; or &#8220;I&#8221;. Substituting a look-alike number for a letter ensures your password won&#8217;t be looked up in an online dictionary. The numeral &#8220;5&#8221; looks like &#8220;S,&#8221; &#8220;2&#8221; can look like &#8220;Z&#8221; and &#8220;3&#8221; can resembles an &#8220;E&#8221;<\/p>\n\n\n\n<p>.<\/p>\n\n\n\n<p><strong>Substitute special characters for letters or numbers<\/strong>: Concurrently, you can try substituting a &#8220;$&#8221; sign for a capital S, an &#8220;!&#8221; for a lower case l or upper case I. You could even use the symbolic version of a word. For instance, use a &#8220;$&#8221; for the word &#8220;dollar,&#8221; &#8220;&amp;&#8221; for &#8220;and,&#8221; and &#8220;@&#8221; for &#8220;at&#8221; or vice versa.<\/p>\n\n\n\n<p><strong>Splitting Words<\/strong>: A simple word or phrase with some sort of significance to you can be a good starting point. You can then &#8220;split&#8221; the word with a number or special character. For example, I watch a show called &#8220;The War at Home&#8221;. A good password based on this would be &#8220;War@H0m3&#8221;.<\/p>\n\n\n\n<p><strong>Favorite Movie or Quote<\/strong>: Take a favorite song, movie or quote. Remove the first letter of each word, up to eight words. Throw away the rest. Example: Star Wars: The Empire Strikes Back, Episode 5. This could be &#8220;SWt3$be5&#8221;.<\/p>\n\n\n\n<p><strong>Foreign Language<\/strong>: For those of you fortunate enough to know two languages, try mixing two words from different languages. (Can&#8217;t really help you here, but get creative)<\/p>\n\n\n\n<p>As an added precaution, Microsoft recommends you change your passwords every 90 days. A server can be configured to prompt you when your network password is about to expire and will prompt you to change it when the time comes. In most cases, you&#8217;ll have up to 14 days to make the change.&nbsp;<em>Hint: Whenever possible, try to reset passwords on a Monday. This will give you the rest of the week to dedicate them to memory.<\/em><\/p>\n\n\n\n<p>Please remember, building strong passwords helps you protect both business and personal data from unauthorized access and passwords are meaningless if you write them down and leave them somewhere easily accessible by others. I cannot over emphasize the importance of this enough. Proper password creation and management isn&#8217;t as daunting a task as you might think. Whenever you need to create a password just remember these three simple rules.<\/p>\n\n\n\n<p>Your passwords should be:<\/p>\n\n\n\n<ol>\n<li>Easy to remember<\/li>\n\n\n\n<li>Difficult for others to guess<\/li>\n\n\n\n<li>Most importantly, never shared<\/li>\n<\/ol>\n\n\n\n<p>I hope you found this helpful!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Building strong passwords helps you protect both business and personal data from unauthorized access. But passwords are meaningless if they are too simple or written down where other can access them. Ronald V. Pacchiano Earlier this week I was at a client site setting up a PC for a new user. Everything was going fine until the system needed to be authenticated to the network. In order to accomplish this, you need to be using an account with administrative privileges. The one I was using didn&#8217;t. This meant that I would need to have the office manager handle this part <\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"_links":{"self":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/7294"}],"collection":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/comments?post=7294"}],"version-history":[{"count":1,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/7294\/revisions"}],"predecessor-version":[{"id":7295,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/posts\/7294\/revisions\/7295"}],"wp:attachment":[{"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/media?parent=7294"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/categories?post=7294"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.practicallynetworked.com\/wp-json\/wp\/v2\/tags?post=7294"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}