Attacks/Breaches
5/2/2013
02:31 PM
Connect Directly
LinkedIn
Twitter
Google+
RSS
E-Mail
50%
50%

Facebook Turns Friends Into IT Support

Facebook's new Trusted Contacts option lets friends assist with account recovery, so Facebook personnel don't have to.

Microsoft Surface: Round Two
10 Ways Microsoft Could Improve Surface Tablet
(click image for larger view and for slideshow)
Just as companies have warmed to the financial benefits of employee-supplied devices and have embraced the rent savings of offices that are open but smaller under the pretense of promoting interaction, Facebook has recognized the economic and security promise of deputizing users to provide customer support.

The social network, ever keen to increase user engagement, wants you to designate friends as Trusted Contacts who can restore access to your Facebook account "if you ever have trouble logging in." Don't call us, call a friend.

Why might you have trouble logging in? Facebook doesn't say. A hacked account is one possibility, but presumably anyone who hijacks your account could alter your Trusted Contact list. And Facebook maintains a separate account reset process for hacked accounts, at facebook.com/hacked.

[ Wondering what it's like to wear Google's new high-tech glasses? Read Google Glass: First Impressions. ]

The most common scenario for resorting to Trusted Contacts is a forgotten password. This could be a relatively frequent occurrence, given that Facebook tends to keep users logged in, thereby obviating the need to type one's password and making it easier to forget.

Account recovery processes, however, have a long history of insecurity. For example, in 2008, the Yahoo Mail account of then vice presidential candidate Sarah Palin was hacked when a University of Tennessee student reset the account password by answering what turned out to be obvious password recovery questions. The following year, Yahoo Mail's account recovery process was abused again to gain control over a Twitter administrative account.

A Facebook spokeswoman in an email said that there are also occasions when users lose access to the email account through which they log in to Facebook.

Facebook in a blog post suggests that the Trusted Contact account recovery process represents an improvement on answering security questions. "With trusted contacts, there's no need to worry about remembering the answer to your security question or filling out long web forms to prove who you are," the company says. "You can recover your account with help from your friends."

There's another security benefit too: Account compromises often occur as a result of social engineering attacks. While customer service personnel can be tricked into revealing personal information by people posing as account holders, friends presumably are less likely to be duped by an imposter soliciting sensitive data.

With Trusted Contacts, Facebook support personnel can expect fewer emails from users who can't log in to get their their social fix. What's more, Trusted Contacts could create a user retention halo effect: Users will probably be less likely to drift away from Facebook when their friends have entrusted them with the keys to their accounts.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cara Latham
50%
50%
Cara Latham,
User Rank: Apprentice
5/6/2013 | 12:41:24 PM
re: Facebook Turns Friends Into IT Support
It sounds like a manipulative trick Facebook is playing if the company really is thinking that Trusted Contacts would create a scenario in which users would be "less likely to drift away
from Facebook when their friends have entrusted them with the keys to
their account."

Then again, I think most users would be wary of providing even their "trusted contacts" with access to their accounts. On a small level, think of the possibility of someone posting an obscene status update on your behalf. On a larger level, it could possibly tie you to the site for a long time.

My reaction is to avoid it. I have survived many years without needing to add Trusted Contacts to my account, so I think I will do without them in the future.
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4734
Published: 2014-07-21
Cross-site scripting (XSS) vulnerability in e107_admin/db.php in e107 2.0 alpha2 and earlier allows remote attackers to inject arbitrary web script or HTML via the type parameter.

CVE-2014-4960
Published: 2014-07-21
Multiple SQL injection vulnerabilities in models\gallery.php in Youtube Gallery (com_youtubegallery) component 4.x through 4.1.7, and possibly 3.x, for Joomla! allow remote attackers to execute arbitrary SQL commands via the (1) listid or (2) themeid parameter to index.php.

CVE-2014-5016
Published: 2014-07-21
Multiple cross-site scripting (XSS) vulnerabilities in LimeSurvey 2.05+ Build 140618 allow remote attackers to inject arbitrary web script or HTML via (1) the pid attribute to the getAttribute_json function to application/controllers/admin/participantsaction.php in CPDB, (2) the sa parameter to appl...

CVE-2014-5017
Published: 2014-07-21
SQL injection vulnerability in CPDB in application/controllers/admin/participantsaction.php in LimeSurvey 2.05+ Build 140618 allows remote attackers to execute arbitrary SQL commands via the sidx parameter in a JSON request to admin/participants/sa/getParticipants_json, related to a search parameter...

CVE-2014-5018
Published: 2014-07-21
Incomplete blacklist vulnerability in the autoEscape function in common_helper.php in LimeSurvey 2.05+ Build 140618 allows remote attackers to conduct cross-site scripting (XSS) attacks via the GBK charset in the loadname parameter to index.php, related to the survey resume.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.