Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
11/30/2011
08:38 AM
Dark Reading
Dark Reading
Security Insights
Connect Directly
RSS
E-Mail
50%
50%

Unprotected SCADA Systems An Avoidable Risk

Disconnecting SCADA systems from the Internet prevents opportunistic hacking

Though the Department of Homeland Security isn’t yet ready to call the recent system failure at an Illinois water-processing plant an act of cyberterrorism -- a direct contradiction of an initial report by the Illinois Statewide Terrorism and Intelligence Center, which labeled the event “a cyber intrusion” -- the incident still calls attention to how the U.S. SCADA (supervisory control and data acquisition) infrastructure remains woefully unprotected.

The water pump at the Springfield utility burned out after the SCADA system cycled the pump off and on continuously until it failed, raising an alert to the operators.

Reading about this, my spidey-sense was tingling ... What? They have SCADA control systems hooked up to the public Internet? And they are running phpMyAdmin!?

It would appear it is common practice these days to connect these sensitive critical-infrastructure systems to the public Internet and use COTS (Common Off The Shelf) software to manage them.

Convenience and price are always desirable to those responsible for managing these systems, but this is bordering on criminally negligent when you are responsible for our water, power, gas, and other sensitive utilities.

Quoting Ira Winkler, a penetration-testing consultant and advocate for better SCADA security: “The overriding weakness of these supervisory control and data acquisition systems is that they are ultimately connected to the Internet. They were originally designed to be set up as isolated, but as businesses and utilities using them grew, they connected to their enterprise networks, which in turn connected to the Internet."

That means if attackers can hack into the enterprise network, then from there they can hack into the SCADA network. "I don't know why this is acceptable," Winkler says. "It's devastatingly stupid."

I can’t help but agree with his assessment. In fact, when you drill down far enough, you find there are no regulations on the books that compel owners of these networks to properly secure them. As Winkler also points out, there are guidelines and recommendations and voluntary standards, but nothing with “legal bite” that can issue “penalties for failing to comply.”

The truth is, there are utility companies operating right now where their SCADA systems are hooked up to the Internet, tempting cyber hacks along the same lines with what was reported to have occurred at the Springfield water plant. Manufacturers, integrators, and operators are all at fault here; if a random hacker can break in without any real effort, then can you imagine what a determined adversary might be able to accomplish?

Chester Wisniewski is a senior security adviser at Sophos Canada

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
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
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.