Cloud

1/12/2017
03:00 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
100%
0%

Ex-US National Security Official Clarke: Regulation Key To Protecting ICS/SCADA From Cyberattacks

Richard Clarke proposes a Y2K-style approach to beefing up security for critical infrastructure.

S4 CONFERENCE – Miami, Fla. – Richard Clarke, the former US National Coordinator for Security, Infrastructure Protection and Counterterrorism and White House official under three administrations, in a keynote here today proposed a Y2K-style initiative to tighten security in industrial control system (ICS) networks that would require sites to meet certain security levels by a specific date.

Clarke, who is chairman of security consulting firm Good Harbor, said this security effort would require what he described as the "dirtiest word in Washington:" regulation.

Clarke's regulation recommendation would address a major challenge faced by ICS/SCADA operators: getting the budget and resources to protect industrial control systems from damaging cyberattacks requires convincing upper management or Boards of Directors to plan for the unexpected or never-before seen incidents, Clarke said. 

"You have to persuade your bosses and policymakers that this is a problem even though it's never happened before," he said of the potential for catastrophic cyberattacks and other serious events. Clarke said it's a matter of setting a deadline for when systems must be secured: "What we need as a country to set those goal is to say industry-by industry at a certain date everything deployed has to have a security package on it. Everything deployed after this date will have to have a security package on it," for example, he explained.

It's tough to get execs to fund possible threats that their organizations haven't experienced or that haven't actually occurred yet in ICS/SCADA,  he said. "you've never really had a big cyberattack" on an ICS or SCADA system, which is the problem here, he said. "They want you to put a probablity on that. You have to resist that."

So healthcare, electric power and other ICS systems and connected automobiles would adopt this security policy approach, he said. This phased-in approach addresses the reality that ICS/SCADA systems can't be forklift-updated overnight. "[You] will have to spend money to replace all of the legacy systems … They change every 30 years or more or not," he said. "We have to do something different."

Y2K Flashback
Clarke said the market will adapt to the demands for more secure ICS/SCADA and other systems in critical industries such as healthcare and critical infrastructure.

"We have been here before. We had the Y2K problem," he said, referring to the industry-wide effort prior to Jan. 1, 2000, to update software and systems to accommodate the new century in older computer clocks. "Where we had to go back and change everything…change software … people thought then that was an ambitious goal, but we did it. And we can do it again."

Clarke says the only way to get ICS/SCADA  infrastructures protected from looming threats is to adopt a form of regulation, which he acknowledged was a tall order in the regulatory-averse political environment. "In the absence of regulation, none of this is going to happen," he said. "Regulations aren't always bad."

In the past, they've been badly written and micromanaged, he said, but they can be simpler.

"You come up with the standards and products and the beauty of that is the government is not telling you what to do and everyone has to do it so it doesn't put anyone at a competitive disadvantage," he said.

But Clarke admitted that the chances of this coming together are slim amid an anti-regulatory climate in Washington. "And given that trying to get people to prevent something that has never happened before … so I'm not optimistic. But on the other hand, it's never happened before, either … So maybe that's the thing that's never happened before" that will," he said.

Related Content:

 

Kelly Jackson Higgins is Executive Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
LoriH800
50%
50%
LoriH800,
User Rank: Apprentice
1/18/2017 | 10:40:25 AM
ICS Cyber Attacks
Hi Kelly, I am curious about your starement regarding there have been not been attacks on ICS.  There have been quite a few cyber attacks on ICS's, including two incidents causing power outtages in Ukrania, the most recent (December17, 2016) was a topic of conversation at S4.  Why did you say there had been no attacks?
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.