Vulnerabilities / Threats
3/3/2014
06:58 PM
Connect Directly
RSS
E-Mail
50%
50%

Hacking Critical Infrastructure Companies -- A Pen Tester's View

At the RSA Conference, a penetration tester outlines some of the elements of a successful attack on energy companies

Dramatic attacks can have simple beginnings, even when the target is a critical infrastructure company.

RSA Conference 2014
Click here for more articles about the RSA Conference.

This is certainly true if Andrew Whitaker's experience is any indication. Whitaker is director of penetration-testing services for Knowledge Consulting Group. A the RSA Conference last week in San Francisco, he took the stage and described the ways pen testers pwn, con, and otherwise sneak their way past security.

For Whitaker, it starts with phishing emails targeting SCADA engineers.

"We go after you because you know how to get into the industrial control systems, and we want to find out how are you getting in there," he told attendees. "I could try to brute-force your login credentials, but it's so much easier just to ask."

How much easier? According to Whitaker, 18 percent of the people fall for these password phishing requests -- not an insignificant number, considering the fact that an attacker needs only one set of account credentials to access a network. It could start off with the spoofing of a login page for Microsoft Outlook Web Access, for example.

The email would include a link to the spoofed page and pretend to come from a system administrator requesting the user follow the link and log on for some reason. When a user does that, his or her username and password would be captured.

The most effective phishing emails are short and sweet, he explains.

"What we've discovered is that when you do really long phishing emails, if somebody knows the sys admin, they are going to read it and go, that doesn't sound like him at all," he says. "So keeping it short [and] to the point has been far more effective."

That is far from a shock to Rohyt Belani, CEO of security firm PhishMe.

"The most effective phishing emails take a tone of authority and instill a sense of urgency -- for example, threatening to lock a user account if the password is not reset," he told Dark Reading in an interview. "Based on our experience training more than 5 million users, phishing emails that create urgency by threatening negative consequences are 20 to 25 percent more effective than emails that offer the recipient some kind of reward."

When training to spot phishers, most organizations focus on technical details, such as recognizing malicious URLs and headers, Belani says. While that's important, the first step should be to instill a healthy dose of suspicion.

"Users should first ask themselves whether they tried to reset their password, and, if not, view the email with suspicion," he says, adding employees should notify the IT department if the email is questionable. "It's possible that an attacker is trying to reset their account, but this is most likely a phishing email."

But the social engineering employed by Whitaker's pen testers did not end with clever emails; it continued from there as needed to include pen testers getting inside the building using fake employee badges and ruses, such as pretending to be support staff for a company performing network monitoring for one of its targets. Then there was always the prospect of sneaking in the door behind employees smoking outside.

"For me, I don't smoke anymore. I used to," Whitaker says. "But I will smoke in order to hack into your building."

Once inside, the pen testers were able to wander around buildings. Getting around can be tricky, but a good supply of canned air can help.

"You guys know those doors that have the badge access, but then on the other side there is a sensor, so when someone's coming up, it senses them and then automatically unlocks the door? Well, this is an old pen-tester secret -- you take the can of air and you just spray it along the crack of the door. It triggers the sensor, and now you can get in," Whitaker says.

The ultimate goal, of course, is to get access to the SCADA network.

"We'll target the SCADA engineers," he explains. "We just spy on them. We'll spend an entire day ... just monitoring that engineer. We want to find out how they are getting in. We may take screenshots. We may inject keyloggers."

The bottom line, he says, is that critical infrastructure companies need to do three things: secure their people, involve their people, and invest in their people.

"I would not have been able to get in most of the time if the phishing attacks didn't work," he says. "I would not be able to get in if I did not see the people making these mistakes."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Brian Prince is a freelance writer for a number of IT security-focused publications. Prior to becoming a freelance reporter, he worked at eWEEK for five years covering not only security, but also a variety of other subjects in the tech industry. Before that, he worked as a ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.