Analytics
8/6/2010
10:30 PM
Connect Directly
RSS
E-Mail
50%
50%

Tech Insight: Building The Right Defense Against Social Engineering

Defcon capture-the-flag contest shows humans are still the enterprise's weakest link

Was your company targeted during last week's Social Engineering Capture the Flag event at the Defcon conference? If it was, would you know?

The contest caused quite a stir in several industries -- in fact, the FBI contacted the contest's organizers to discuss concerns that sensitive, personal information would be targeted.

So what's the big deal? Social engineering is certainly nothing new. However, the contest -- and the associated press coverage -- managed to raise a new level of concern. Some companies went as far as to send out information to their employees and customers warning them about the upcoming contest.

We've all used social engineering to get what we want -- even when we were children. Now we're faced by attackers who are using it against our companies to get what they want. The question so many future victims ask is what would an attacker want from them? The answer is simple: information.

Maybe your company is the direct target of an attacker, or maybe it's simply a stepping stone to a bigger fish. Either way, social engineering is the most effective tool that an attacker can use against your company. You can patch every desktop and segregate every sensitive network segment, but you can't accurately predict your employees' behavior when facing a cleverly designed attack.

The best defense against social engineering is awareness and training -- with policies to back both. You and your employees should know the most common technical forms of social engineering attacks. Phishing, instant messaging, and social networks are the three attack vectors your users face.

Those three attack vectors have two things in common: They insulate attackers from face-to-face communications, and they're extremely effective. Novice social engineers often opt for these online methods because they require less skill to perform successfully than talking to a target on the phone or walking through the front door.

Using any of these three vectors, an attacker can entice users into providing their credentials. The most common targets are the places where the credentials are collected via email or through a form on a Website. The attack site is set up to mimic a legitimate site the user would expect to see and trust.

In many cases, users are tricked into thinking there is an urgency to provide their user names and passwords. They fall for a scam that threatens to terminate their access to bank or email accounts; they're convinced to take swift steps to help a co-worker.

Sophisticated social engineering techniques, like those demonstrated in the Social Engineering CTF, require preparation to know details about the target organization and those who work there. But that's not always enough, even when combined with confidence. An understanding of human behaviors is needed, and knowing the correct gestures and language to use in specific situations is often necessary to be successful.

The most common personal attack vectors, as described by the Social Engineering Framework at Social-Engineer.org, include customer service, tech support, and delivery persons. Each of these vectors requires talking to the victims on the phone or interacting in person. This is where attacks often fail because the attacker doesn't know enough about the target -- or fails to gain the victim's confidence.

Chris Hadnagy, organizer of the Social Engineering CTF contest, said, "Every company where we were able to contact a human, [the contestants] were successful at social engineering them." Two employees at a target company did thwart one contestant's efforts because the questions sounded "fishy."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
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-0103
Published: 2014-07-29
WebAccess in Zarafa before 7.1.10 and WebApp before 1.6 stores credentials in cleartext, which allows local Apache users to obtain sensitive information by reading the PHP session files.

CVE-2014-0475
Published: 2014-07-29
Multiple directory traversal vulnerabilities in GNU C Library (aka glibc or libc6) before 2.20 allow context-dependent attackers to bypass ForceCommand restrictions and possibly have other unspecified impact via a .. (dot dot) in a (1) LC_*, (2) LANG, or other locale environment variable.

CVE-2014-0889
Published: 2014-07-29
Multiple cross-site scripting (XSS) vulnerabilities in IBM Atlas Suite (aka Atlas Policy Suite), as used in Atlas eDiscovery Process Management through 6.0.3, Disposal and Governance Management for IT through 6.0.3, and Global Retention Policy and Schedule Management through 6.0.3, allow remote atta...

CVE-2014-2226
Published: 2014-07-29
Ubiquiti UniFi Controller before 3.2.1 logs the administrative password hash in syslog messages, which allows man-in-the-middle attackers to obtains sensitive information via unspecified vectors.

CVE-2014-3020
Published: 2014-07-29
install.sh in the Embedded WebSphere Application Server (eWAS) 7.0 before FP33 in IBM Tivoli Integrated Portal (TIP) 2.1 and 2.2 sets world-writable permissions for the installRoot directory tree, which allows local users to gain privileges via a Trojan horse program.

Best of the Web
Dark Reading Radio