06:41 PM
George V. Hulme
George V. Hulme

Social Networking: Keeping It Real

Another demonstration on the security and privacy implications of using social networking sites reveals their real weakness. And I say: so what.

Another demonstration on the security and privacy implications of using social networking sites reveals their real weakness. And I say: so what.We've all read the stories about the perils of revealing too much information on sites such as Facebook, LinkedIn, and Twitter. We've had experiments presented at Black Hat and Defcon in year's past highlighting how easy it is for fake LinkedIn profiles to befriend a targeted group of people, and numerous conference sessions, such as at this year's RSA Conference about how companies should approach the use of social networking sites at work.

We even had a Web site launch, PleaseRobMe.com, purportedly designed to raise awareness about over-sharing one's where a bouts on social networking sites.

And, earlier this year, the Department of Defense lightened up its harsh stance against social networking sites. There has been a long and queasy relationship with social media and the military - not surprisingly - over security concerns. Still, I was not surprised to read in Tuesday's DarkReading about how a bogus (Robin Sage) LinkedIn, Facebook, and Twitter profile duped a number of (who should have known better) security-aware people:

Robin Sage gained a total of about 300 friends on LinkedIn, counting those who came and went, he says. All three of the phony woman's social networking accounts remain active -- the LinkedIn profile currently has 148 connections, the Facebook profile has 110, and the Twitter account has 141 followers. Ryan officially ran the experiment for 28 days starting in late December and ending in January of this year.

Among Robin's social networking accomplishments: She scored connections with people in the Joint Chiefs of Staff, the CIO of the NSA, an intelligence director for the U.S. Marines, a chief of staff for the U.S. House of Representatives, and several Pentagon and DoD employees. The profiles also attracted defense contractors, such as Lockheed Martin, Northrop Grumman, and Booz Allen Hamilton. Lockheed and other firms made job offers to Robin, some inviting her to dinner to discuss employment prospects. "I was surprised at how people in her same command friended her -- people actually in the same command and the same building," Ryan says.

It doesn't surprise me that a number of security and intelligence professionals fell for the ruse. They've the same weaknesses as any other group of people. And they're going to make mistakes.

But we've reached the point to where these ruses are a bore. It's easy to fool people in most any circle, and to use any gained trust to potentially gather sensitive information. It's too easy, in fact. And those connections can be used to footprint targets and be used for information gathering. We get it.

What's hard is solving the challenge. Coming up with a real, sustainable solution to the social media and security problem.

I don't pretend to have one. Nothing better than improving awareness, anyway. Organizations need to remind people that the internet is public, and that the only safe decision is to post information that is safe for the world to see. And that users of LinkedIn, Facebook and others should be wary of whom they connect with. I'll often go so far as to send an e-mail or call to make sure a person is who they actually claim to be.

But that's not a solution, and it's not good enough. People will always succumb to social engineering attacks on social networks.

Perhaps the time has come for social media sites to provide a reputation score for their profiles. Profiles could increase their reputation over time, by having others vouch for the profile and the user, and perhaps even having the identities verified. Users could still have anonymous profiles, but they'd suffer a lower reputation as a trade-off.

I haven't thought the idea through much more than knowing the current way of doing things just isn't working. I'm open for improvements, and entirely new ideas. That'd be much more helpful than repeatedly proving what we already know.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Current Issue
Dark Reading Tech Digest September 7, 2015
Some security flaws go beyond simple app vulnerabilities. Have you checked for these?
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
Published: 2015-10-12
vpxd in VMware vCenter Server 5.0 before u3e, 5.1 before u3, and 5.5 before u2 allows remote attackers to cause a denial of service via a long heartbeat message.

Published: 2015-10-12
The JMX RMI service in VMware vCenter Server 5.0 before u3e, 5.1 before u3b, 5.5 before u3, and 6.0 before u1 does not restrict registration of MBeans, which allows remote attackers to execute arbitrary code via the RMI protocol.

Published: 2015-10-12
Cisco Unified Computing System (UCS) B Blade Server Software 2.2.x before 2.2.6 allows local users to cause a denial of service (host OS or BMC hang) by sending crafted packets over the Inter-IC (I2C) bus, aka Bug ID CSCuq77241.

Published: 2015-10-12
The process-management implementation in Cisco TelePresence Video Communication Server (VCS) Expressway X8.5.2 allows local users to gain privileges by terminating a firestarter.py supervised process and then triggering the restart of a process by the root account, aka Bug ID CSCuv12272.

Published: 2015-10-12
HP 3PAR Service Processor SP 4.2.0.GA-29 (GA) SPOCC, SP 4.3.0.GA-17 (GA) SPOCC, and SP 4.3.0-GA-24 (MU1) SPOCC allows remote authenticated users to obtain sensitive information via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
What can the information security industry do to solve the IoT security problem? Learn more and join the conversation on the next episode of Dark Reading Radio.