Attacks/Breaches
8/14/2012
09:50 AM
50%
50%

5 Ways To Solve The Password Reset Problem

Apple, Amazon, and other vendors need to come up with better ways to safeguard accounts against social engineering attacks. But users must help.

Technology companies and retailers that sell goods and services to consumers--including cell phone plans, books and music, online file-storage lockers, and cloud-based collaboration software--have a password security problem.

The nature of the problem was highlighted by the recent hack of technology journalist Mat Honan, who saw his laptop, tablet, and smartphone get remotely wiped by an attacker--dubbed "Phobia"--who was trying to keep Honan from regaining access to the three-letter Twitter account ("mat") that Phobia hacked for fun.

In today's ultra-connected digital world, Honan's fatal information security flaw was to have left a single point of failure--a Gmail account tied to an iCloud account--that Phobia was able to compromise. True, Phobia first socially engineered Amazon into providing the information he needed to impersonate Honan with Apple (name, address, and last four digits of the credit card on file), before resetting passwords and "owing" Honan's digital life.

But this security issue isn't limited to the companies that featured in that life hack of Honan. "Everyone is pointing the finger at Amazon and Apple, saying it's a big security hole, they need to make changes. But I don't look at it that way--if it's a security hole, it affects a lot more companies than Amazon," says the threat intelligence manager for Trustwave SpiderLabs, who goes by "Space Rogue," speaking by phone. Indeed, most companies will reset users' passwords by phone, provided you know a user's name, address, and the last four digits of their on-file credit card number. Most banks, meanwhile, require the last four digits of a person's social security number, instead of their credit card.

[ Get more good advice. Read 8 Ways To Avoid Getting Your Life Hacked. ]

Given that lackluster state of consumer identity verification, here are five must-have password security practices that every company and consumer should practice:

1. Deploy background-verification security checks.

To make it more difficult for social engineers to successfully impersonate consumers, more companies have been validating people's identity by asking such questions as, "Which of the following five addresses is associated with your name?"

Such security checks are enabled via services that first comb publicly available information to find "digital fingerprints" that are likely associated with a specific person. One such service is RSA Identity Verification, which RSA bills as "dynamic, knowledge-based authentication to validate user identities and reduce the risk of identity impersonation and fraud."

2. Employ "do it yourself" secret questions.

Too many businesses ask people the same questions: mother's maiden name, or the name of their first school, town in which they were born, or favorite pet. Why not shake things up? "My cell phone company, if I call up AT&T, and ask to make a change to my account, they ask for a secret password--they have a password they asked for when I created my account that's 'secret' and which I provided when I first set up the account," says Space Rogue.

3. Resets trigger massive warnings.

Want to change your password? Then the service in question should blast a password-reset warning to every device you own. "Ideally, before resetting a password by phone, they'd send a forced 'Find My'-style push alert to all registered devices on the account saying something like, "Apple Customer Service has received a request to reset your iCloud password. Please call 1-800-WHATEVER within 24 hours if this is unauthorized," says Marco Arment, the co-founder of Tumblr, in a blog post. As that suggests, he also recommends that anyone who wants to rest a password by phone be made to wait 24 hours, to give ample time to alert potential victims.

4. Consumers: Use lots of different credit cards.

One way that Phobia was able to successfully hack Honan was thanks to Honan having used the same credit card at Apple and Amazon. By seeing the last four digits of the card--displayed by Amazon, when users access their account--Phobia was then able to provide it to Apple to authenticate himself as Honan. "If the card [Honan] stored with Amazon didn't match the card stored with Apple, the attack would have stopped here," says Rob Sobers, technical manager at Varonis Systems, via email. To help prevent such attacks, he says, "you could dedicate a single purpose credit card for Apple."

"Personally I use a different credit card and email address at Paypal, Amazon, and Apple," says Trustwave's Space Rogue. "It isn't foolproof but it does make things more difficult."

5. Consumers: Enable two-factor Gmail authentication.

While Gmail featured in the hack of Honan, he notably didn't have two-factor authentication turned on. But if he had, it would likely have blocked the attacker. In fact, Space Rogue specifically recommends that all Gmail users employ their accounts for any services that are tied to bank or credit card accounts, such as Amazon or online banking, thanks to the added security. "Use Gmail as the address for any accounts that can access money and turn on the free two-factor authentication they offer," he says. Also don't forget to use different passwords for every one of those sites too.

But too many sites--including Amazon and Apple--still don't offer two-factor authentication. While it's not a silver bullet, it would be better than the current username and password protection both sites offer.

Amazon and Apple are both reportedly revisiting their password-reset practices, but many more companies will have to pursue similar changes to protect their customers from "life hack" attacks. Beyond the above five recommendations, what should all businesses be doing--or doing better--to safeguard consumers' identities?

One of the biggest challenges facing IT today is risk assessment. Risk measurement and impact assessment aren't exact sciences, but there are tools, processes, and principles that can be leveraged to ensure that organizations are well-protected and that senior management is well-informed. In our Measuring Risk: A Security Pro's Guide report, we recommend tools for evaluating security risks and provide some ideas for effectively putting the resulting data into business context. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
TS_Time
50%
50%
TS_Time,
User Rank: Apprentice
8/24/2012 | 12:27:27 PM
re: 5 Ways To Solve The Password Reset Problem
Email password resets in my opinion need to be authenticated. When someone wants to reset their password, the site should have a form of 2FA where the person receives by SMS a one-time password that they use to telesign into their account to reset the account password. That way if their secondary email has been compromised the hacker will not be able to gain control without the OTP. I use Two-Factor Authentication across a lot of my accounts. I feel a lot more secure when I can telesign into my account. If you have that option available to you use it, it is worth the time and effort to have the confidence that your account won't get hacked and your personal information isn't up for grabs. I'm hoping that more companies start to offer this awesome functionality. This should be a prerequisite to any system that wants to promote itself as being secure.
Aroper-VEC
50%
50%
Aroper-VEC,
User Rank: Apprentice
8/1/2013 | 4:31:22 PM
re: 5 Ways To Solve The Password Reset Problem
Apple has improved security practices. Two-factor authentication is now available so this article is technically inaccurate. See this FAQ for more information: http://support.apple.com/kb/HT...
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: nice post
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-1750
Published: 2015-07-01
Open redirect vulnerability in nokia-mapsplaces.php in the Nokia Maps & Places plugin 1.6.6 for WordPress allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the href parameter to page/place.html. NOTE: this was originally reported as cross-sit...

CVE-2014-1836
Published: 2015-07-01
Absolute path traversal vulnerability in htdocs/libraries/image-editor/image-edit.php in ImpressCMS before 1.3.6 allows remote attackers to delete arbitrary files via a full pathname in the image_path parameter in a cancel action.

CVE-2015-0848
Published: 2015-07-01
Heap-based buffer overflow in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted BMP image.

CVE-2015-1330
Published: 2015-07-01
unattended-upgrades before 0.86.1 does not properly authenticate packages when the (1) force-confold or (2) force-confnew dpkg options are enabled in the DPkg::Options::* apt configuration, which allows remote man-in-the-middle attackers to upload and execute arbitrary packages via unspecified vecto...

CVE-2015-1950
Published: 2015-07-01
IBM PowerVC Standard Edition 1.2.2.1 through 1.2.2.2 does not require authentication for access to the Python interpreter with nova credentials, which allows KVM guest OS users to discover certain PowerVC credentials and bypass intended access restrictions via unspecified Python code.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report