Title: The future of personal security Post by: HCK on September 07, 2014, 09:00:30 am The future of personal security
<div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even" property="content:encoded"><p><a href='http://www.imore.com/future-personal-security' title="The future of personal security"><img src='http://www.imore.com/sites/imore.com/files/styles/large/public/field/image/2013/07/ios_7_activation_lock_hero.jpg?itok=730pO2V_' />[/url]</p> <p>Apple is responding (http://www.imore.com/tim-cook-says-apple-will-add-more-security-alerts-broaden-2-step-verification-increase-awareness) to security concerns raised by many this past week as a result of massive release of stolen celebrity photos (http://www.imore.com/editors-desk-massive-celebrity-nude-photo-theft-journalistic-failure-and-what-you-need-know). While this is a good move by Apple that will increase security for users, it's important to understand what these changes do and don't mean for us.<!--break--></p> <h2>The more you know ≡≡≡★</h2> <p>Apple was heavily criticized this last week for its security around iCloud backups. iCloud backups can be downloaded with a person's username and password — no two-factor authentication required even for users who have it enabled. In response, Tim Cook announced some upcoming changes to iCloud account security. The first change is starting In a couple of weeks — two-factor authentication will be required when restoring backups from accounts that have two-factor authentication enabled. Additionally, when an iCloud backup is being restored, users will be notified via email and push notification. This are both welcome changes but it's important to remember our role and responsibility in security as users. Speaking to the Wall Street Journal (http://m.us.wsj.com/article_email/tim-cook-says-apple-to-add-security-alerts-for-icloud-users-1409880977-lMyQjAxMTA0MDAwNDEwNDQyWj?mobile=y) on these new changes, Tim Cook said:</p> <p>When I step back from this terrible scenario that happened and say what more could we have done, I think about the awareness piece. I think we have a responsibility to ratchet that up. That's not really an engineering thing.</p><p>I don't think that the importance of this observation can be overstated. With the iCloud accounts that were compromised in relation to the theft and release of celebrity photos, attackers were able to gain access to the accounts by answering security questions. If two-factor authentication had been enabled on those accounts, it would have been significantly more difficult for the attackers to access those accounts because the unique recovery key that users are given when setting up two-factor authentication would have been required before the attackers could have answered the security questions.</p> <p>To be clear, the people who committed these crimes are the only ones responsible for them. I simply want to emphasize that there are steps we can all take to try and better protect ourselves. If people don't know about two-factor authentication, they won't use it. Even if they know about it, if it's easy to ignore then most will not use it. It's important that two-factor authentication be easy to use, and that people are informed about it.</p> <p>Fortunately, the WSJ also said that Apple plans to more aggressively encourage people to enable two-factor authentication in iOS 8. If I had to guess I would say this change might look similar to Apple's change to setting a passcode in iOS 6. Prior to iOS 6, during setup, users would be given two options: Set a passcode on the device or not. Both carried equal weight. In iOS 6, users were instead presented with a keypad to set their passcode. In the upper-right hand corner was a small "Skip" button. People still have the option to not set a passcode, but Apple did a nice job of steering people strongly toward setting one. I would not be surprised to see something similar for two-factor authentication in iOS 8.</p> <p>Even if more people enable two-factor authentication as a result, it's important that they are educated about it. Starting in two weeks Apple will send you a notification when a user attempts to restore an iCloud backup from your account. This notification is a critical piece of informing us as users that somebody could be trying to access our data, but that's all it's doing: informing us. So now what? To some it may seem obvious that it means you should change your password, but to many a simple warning won't mean much. Once again with a bit of good news, Apple also told the WallStreet Journal that the new notification system they will be rolling out in a couple of weeks will give people the chance to take action when they receive a notification, such as changing their password and alerting Apple's security team.</p> <p>As with most things security, this does have a potential negative impact on convenience. If you only have a single device that you've set as a trusted device on your account — let's say your iPhone — and something happens to it — like it's stolen or falls into a river — it will be absolutely essential that you have the recovery key Apple gave you when you enabled two-factor authentication. I think this is a perfectly fair trade-off on Apple's part and I don't think we'll see a large number of people who completely lose access to their iCloud data as a result of two-factor authentication, but I'm guessing the number will be greater than zero.</p> <h2>Token security</h2> <p>Of course we're still not entirely safe (nor will we ever be). Apple's two-factor authentication only uses 4-digit codes. You only get 10 attempts to enter the code before you're locked out for 8 hours, but consider the following. Let's say an attacker has obtained a large number of iCloud account credentials – for the purposes of this exercise we'll say they have 1,000 compromised accounts. Four-digit codes only leave us with 10,000 possible codes. If an attacker can attempt 10 codes on each of those 1,000 accounts, that means they stand a 1 in 1,000 chance of guessing the correct code on any given account. With 1,000 accounts, the attacker has a good chance of correctly guessing the code on at least one of those accounts.</p> <p>This isn't a reason to panic. It's no small feat to obtain credentials for 1,000 iCloud accounts. And even if your account was one of the thousand, there's only a 1 in 1,000 chance that yours would be the one that they would compromise. But still, this is a plausible scenario. Most other services utilizing two-factor authentication seem to use longer codes (6 digits or more). Given the infrequency with which a two-factor authentication code needs to be entered, and how quick it is to enter a numerical code, it would be great see Apple extend the length of their two-factor authentication codes.</p> <h2>No silver bullets</h2> <p>Even with the upcoming changes, two-factor authentication does not guarantee our safety. One of the best things we can do to protect ourselves is use complex, hard to guess, and hard to crack passwords. Just because you have an alarm on your house doesn't mean you should leave your front door unlocked. Two-factor authentication is not intended to replace passwords; it's meant to supplement them.</p> <p>It's been said countless times before, but I'll say it again here: You need to be using long, complex, hard to guess passwords. For most websites and services, I have 1Password generate a long, random password for me. Since your iCloud password is something you need to type in on a fairly regular basis, this may not be the best way to go, but you still need to make it secure. While character complexity is good (mixed case, special characters, numbers), length generally has a greater impact. A phrase like "My dog's name is Scott." is significantly more difficult to crack than a random password like wJM2=.VkN7 (assuming your dog's name isn't actually Scott, in which case that phrase could be easier to guess). Phrases also have the benefit of being easier for our human brains to remember. If you're not sure how to come up with a secure password, there are some great articles out there to help you (http://www.imore.com/how-to-secure-iphone-ipad-strong-alphanumeric-password).</p> <p>If you're one of those people who sees this advice time and time again and thinks "I know I should, but it just seems like too much of a pain", please give it a try. You'd be surprised how quickly you can get used to typing a more complex password.</p> <h2>Insecurity Questions</h2> <p>One final weakness that anybody using iCloud (as well as many other services) should be aware of is security questions. Which do you think would be harder for an attacker to figure out: a password like Ci<s}e)Ob+noks or the answer to the question "What was the name of your first pet?" The problem with security questions is they are significantly easier to learn or guess than good passwords. Often times the answers to security questions can be discovered through casual conversation, or by Googling or looking at your Facebook page. Your account will only be as safe as the weakest link defending it. In order to not have security questions be a weak link, it's a good idea to treat them as passwords.</p> <p>As Rene has previously said (http://www.imore.com/icloud-security-and-personal-responsibility), security questions should be avoided when possible, and when they can't, use randomly generated passwords for the answers (or a long phrase as mentioned above). Just be sure to store these passwords in your favorite password manager so you don't inadvertently lock yourself out of your account.</p> <h2>Looking to the future</h2> <p>Security is a war with no end in sight. It's a cat and mouse game. New vulnerabilities will be discovered, software vendors will patch them, and more new vulnerabilities will arise. As more people around the world continue to use smartphones, more services pop up to store our data, and we continue store more information than ever before on electronic devices, the potential payout for exploiting, and therefore the number of interested criminals, will continue to rise.</p> <p>At this very moment, we have a record amount of digital information stored on servers and in devices, and tomorrow will be a new record. For most of us, simply not using these devices and services is not a viable option. So we move on the best we can. Researchers will continue to promote best security practices, and we should do our best to follow them. Make smart choices.</p> <p>Do everything you can to make yourself a difficult target. Lastly, security is constantly changing and evolving — keep an eye out for changes that take place and new best practices. This will help you stay one step ahead.</p> </div></div></div><div id="comment-wrapper-nid-26794"></div><img width='1' height='1' src='http://tipb.com.feedsportal.com/c/33998/f/616881/s/3e37254e/sc/4/mf.gif' border='0'/><br clear='all'/> <a href="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/1/rc.htm" rel="nofollow"><img src="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/1/rc.img" border="0"/>[/url] <a href="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/2/rc.htm" rel="nofollow"><img src="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/2/rc.img" border="0"/>[/url] <a href="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/3/rc.htm" rel="nofollow"><img src="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/rc/3/rc.img" border="0"/>[/url] <img src="http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/a2.img" border="0"/> (http://da.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/a2.htm)<img width="1" height="1" src="http://pi.feedsportal.com/r/204367352318/u/49/f/616881/c/33998/s/3e37254e/sc/4/a2t.img" border="0"/><img src="http://feeds.feedburner.com/~r/TheIphoneBlog/~4/4JRb777MUC0" height="1" width="1"/> Source: The future of personal security (http://feedproxy.google.com/~r/TheIphoneBlog/~3/4JRb777MUC0/story01.htm) |