Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

4/7/2009
06:18 PM
Gadi Evron
Gadi Evron
Commentary
Connect Directly
Twitter
LinkedIn
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. Gadi is CEO and founder of Cymmetria, a cyber deception startup and chairman of the Israeli CERT. Previously, he was vice president of cybersecurity strategy for Kaspersky Lab and led PwC's Cyber Security Center of Excellence, located in Israel. He is widely recognized for ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.