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

10/11/2018
10:30 AM
Satish Gannu
Satish Gannu
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

The Better Way: Threat Analysis & IIoT Security

Threat analysis offers a more nuanced and multidimensional approach than go/no-go patching in the Industrial Internet of Things. But first, vendors must agree on how they report and address vulnerabilities.

The best approach for securing operational technology is to, first, examine OT's significant security challenges in a far more discriminating manner than the industry currently does. I propose that we use the time-tested threat analysis approach to patching OT systems that can't simply be patched the way IT systems are, for many reasons.

The first step in threat analysis would be to hold off taking any immediate action — patching, not patching, something else — until we validate if a system vulnerability actually exists and, if it does, how it can be exploited.

There are multiple factors to consider. For one, some systems that operate deep inside enterprises may indeed have vulnerabilities, but because the system is so isolated within the enterprise, the actual security risk is less than the risk of shutting the systems down for patching, assuming patches exist.

The calculus changes, of course, when evaluating systems that are exposed to the cloud or the Internet, where the security risk is obviously much greater. Threat analysis would identify which systems can probably go on operating without patches, and which need to be stopped for patching.

Threat analysis would also validate a vulnerability, but it is important to ask another question: If this vulnerability can be exploited by certain threats, is there a way to protect from those threats short of patching? For example, security experts could create a set of predetermined scripts within the network, or on the endpoint device itself, that would help identify the appropriate response to a number of different threats. These scripts would serve as an "if/then" template to formalize, automate, and accelerate responses to threats. The point is to think with more sophistication than a binary patch/don't patch decision.

Wanted: Better Patch Info
Software companies must support the development of threat analysis by telling customers more about the patches they release. Key pieces of information we'd like to see are how vulnerabilities can be exploited and possible ways to protect against them. This extra transparency would give customers more information to make decisions on the right security actions for affected systems. Security experts need to be confident a patch will, at the very least, maintain the same risk level that existed before a vulnerability was discovered.

Threat analysis must be extremely granular. If an enterprise has 100 devices running, each one requires its own threat analysis, which would include a comparison of vulnerabilities versus patch benefits, as well as a resulting menu of security options. The primary goal, of course, is to enhance security while at the same time maximizing OT uptime.

Clearly, threat analysis is more nuanced and multidimensional than go/no-go patching decisions. But it's a challenge the industry must solve to get from where we are to where we should be. Right now, following the process described above takes time, costs money, requires highly skilled professionals — and even then, it's not easy to do. However, if the vendor community agreed upon a set of standards on how it reports and addresses vulnerabilities, this entire process could be automated. 

Some security approaches developed in IT port beautifully to OT, but in this case, patching, what worked so well in IT doesn't entirely fit OT — and now it's time for industry-wide innovation beyond the choice between patch, patch, patch or letting unpatched systems run vulnerably. Our goal must be to build powerful, effective processes, and then automate them to put this new approach within the reach of industrial companies and nations on a global basis. Just because we can see this better future clearly doesn't mean it is close. But let's start now to get there, together.

Related Content:

 

Black Hat Europe returns to London Dec. 3-6, 2018, with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Satish joined San Jose-based ABB in February 2017 as chief security officer and Group VP, architecture and analytics, ABB Ability™, responsible for the security of all products, services and cybersecurity services. Satish brings to this position a background in computer ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8003
PUBLISHED: 2020-01-27
A double-free vulnerability in vrend_renderer.c in virglrenderer through 0.8.1 allows attackers to cause a denial of service by triggering texture allocation failure, because vrend_renderer_resource_allocated_texture is not an appropriate place for a free.
CVE-2019-20427
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has a buffer overflow and panic, and possibly remote code execution, due to the lack of validation for specific fields of packets sent by a client. Interaction between req_capsule_get_size and tgt_brw_write leads to a tgt_shortio2pages integ...
CVE-2019-20428
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds read and panic due to the lack of validation for specific fields of packets sent by a client. The ldl_request_cancel function mishandles a large lock_count parameter.
CVE-2019-20429
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the ptlrpc module has an out-of-bounds read and panic (via a modified lm_bufcount field) due to the lack of validation for specific fields of packets sent by a client. This is caused by interaction between sptlrpc_svc_unwrap_request and lustre_msg_hdr_size_v2...
CVE-2019-20430
PUBLISHED: 2020-01-27
In the Lustre file system before 2.12.3, the mdt module has an LBUG panic (via a large MDT Body eadatasize field) due to the lack of validation for specific fields of packets sent by a client.