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 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.