Perimeter
4/7/2009
06:18 PM
Gadi Evron
Gadi Evron
Commentary
Connect Directly
RSS
E-Mail
50%
50%

SCADA Security: What SCADA Security?

SCADA, the control systems for such infrastructure services as water and energy, has us worried whenever critical infrastructure defense is mentioned. Why, then, is it the most insecure industry on the planet?

SCADA, the control systems for such infrastructure services as water and energy, has us worried whenever critical infrastructure defense is mentioned. Why, then, is it the most insecure industry on the planet?SCADA security is as crucial as ever today with cyberattacks on the rise, including those that are apparently state-sponsored. And without contest, SCADA is a major target, with the most potential damage to the economy and to daily life.

Many efforts are in the works to increase the security of SCADA systems, but I do not see any measurable results. Lack of security processes, such as secure coding, auditing, and modern patch distribution systems, are some examples, but the most telling one is how SCADA vendors treat software vulnerabilities.

SCADA security vulnerability-handling is a sham as it stands today. In the 1990s, Bugtraq and other forums introduced the concept of openly releasing vulnerability information on products from IT vendors in full disclosure. Ten years later, many of these vendors acknowledge reports, work with researchers to solve the issues, and provide their clients with relevant information and patches in a timely fashion. Today many software vendors act responsibly, and full disclosure has mostly become a matter of choice.

This model may not work with SCADA, however. How do you release information when a SCADA vendor will not patch the vulnerability? Misuse can seriously damage civilian infrastructure.

Full disclosure is a public-shaming technique. Perhaps another sort of public shaming could be introduced?

One idea is to create a centralized reporting Website where SCADA vulnerabilities are tracked (with whatever information can be made public), and the vendors can be called out for their slow response and patching time.

SCADA operators say taking a plant offline is unacceptable. In my opinion, the threat is serious enough to make security top priority. If it were a priority, then SCADA systems would be designed so that patching can be done without a shutdown.

Unless an alternative is found, I will soon be of the opinion that for us to be safe two or even 20 years in the future -- when the world is even more connected -- public shaming on SCADA system vulnerabilities is the only alternative to waking up to a digital 9/11 or Pearl Harbor.

Follow Gadi Evron on Twitter: http://twitter.com/gadievron

Gadi Evron is an independent security strategist based in Israel. Special to Dark Reading.

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-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.