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.

Risk

8/28/2019
10:30 AM
Vivek Shah
Vivek Shah
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

Securing Our Infrastructure: 3 Steps OEMs Must Take in the IoT Age

Security has lagged behind adoption of the Internet of Things. The devices hold much promise, but only if a comprehensive security model is constructed.

As adoption of the Internet of Things (IoT) and the Industrial Internet of Things (IIoT) ramps up, the cybersecurity threat landscape changes from PCs, tablets, and conventional networks to all sorts of connected devices, including large, durable goods (think airplanes, automobiles, and construction equipment). IIoT connects major equipment such as aircraft, automobiles, and critical pieces of national infrastructure, including turbines used in power generation and transformers and switches in our electricity grid.

Cisco estimates that the number of devices connected to IP networks will be more than three times the global population by 2022, in the range of 30 billion to 50 billion, with a projected annual economic impact of $3.9 trillion to $11.1 trillion worldwide by 2025. Even if growth projections are overly optimistic, cybersecurity must assume a much more critical role. If a piece of durable machinery becomes infected, the consequences pose a serious threat to business performance and production, as well as overall safety — and could even have national security implications. As older, unconnected equipment is replaced with new, connected machinery, fears are beginning to rise about how secure this new equipment is and what can be done to make it more impregnable from cyberattacks.

Here are three things that original equipment manufacturers (OEMs) should focus on to enhance data security, while also fully realizing the promised economic benefits of IoT and IIoT.

1. Adopt Industrywide Standards
In the software world, we design with security in mind and adhere to a set of well-defined and mature industry standards that allow for different parts of the technology stack to interact with each other. However, the industrial manufacturing world lacks overarching standards for IoT. Instead, in certain industries, there is often competition between large players who rely on a small set of proprietary and incompatible technology standards. This lack of common standards makes it difficult to develop end-to-end security. The manufacturing industry needs to follow the software industry’s lead and come together to define standards. Equipment is becoming increasingly complex with millions of lines of code and the introduction of more equipment that’s designed with software in mind. OEMs must work more closely with suppliers and industry organizations to accelerate the development of industry standards for the greater benefit of everyone.

2. Improve Communication and Sophistication
In the manufacturing world, specifically the operations technology (OT) sphere, legacy operational standards such as OPC and Modbus are still in use today but were designed more than 20 years ago using old technologies, including COM. They were not designed for communication over modern IP networks with multiple security layers and, due to a general lack of cybersecurity sophistication, traditional OT networks have most security options disabled to simplify configuration.

By its nature, a large open network of connected devices opens many new attack vector threats, even if individual devices may be secure when used independently. Because the weakest point in the system determines its overall security level, a comprehensive end-to-end approach is required to secure it. The lack of industry standards within the manufacturing space makes it difficult to develop such an approach because hackers concentrate on breaching a specific element within the technology stack.

To combat this, manufacturers must adopt a similar standard to what’s found within the software industry, where communication networks are completely closed and ports are only opened as needed, and comprehensive end-to-end approaches are designed. Traditional industrial component suppliers and OEMs are not well positioned to perform this task, but the industry has to improve its level of sophistication to provide end-to-end protection against all types of attack vector threats.

3. Increased Focus on On-Device Security, Leveraging IoT Strengths
While network-level or cloud infrastructure cybersecurity is very important, manufacturers also must realize that device-level cybersecurity is equally or more important. Most data is still stored in the cloud, yet manufacturers must come to terms with data and information also being stored directly on devices themselves. This means a "cloud only" cybersecurity strategy won’t get the job done.

Endpoint security solutions designed for smartphones and tablets can't be expected to work for IoT sensors and devices because the design of IoT devices makes this unfeasible at a typical enterprise level. Manufacturers need a combination of network-level security and solutions tailored specifically for IoT architectures, including sensor devices. One of the biggest strengths of IoT is the sheer amount of data that devices are expected to generate, and this same strength could be used to apply machine learning models to detect anomalous malicious behavior that could compromise security.

IoT technology is one of the most exciting disruptions to hit the manufacturing space in years. However, security has lagged behind technology adoption, and if we don't r-think and adopt a new comprehensive security model for connected devices, the value that IoT promises to deliver will just remain that — a promise. By implementing the steps above, OEMs and industry can better prepare for cybersecurity challenges and have more peace of mind when adopting IoT technology.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "The Right to Be Patched: How Sentient Robots Will Change InfoSec Management."

Vivek Shah is the Senior Product Director at Syncron. For more than 15 years, Vivek has excelled as an IIoT analytics product director and strategist, delivering advanced analytics powered outcomes for digital customers worldwide. He has served industries ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
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
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-18980
PUBLISHED: 2019-11-14
On Signify Philips Taolight Smart Wi-Fi Wiz Connected LED Bulb 9290022656 devices, an unprotected API lets remote users control the bulb's operation. Anyone can turn the bulb on or off, or change its color or brightness remotely. There is no authentication or encryption to use the control API. The o...
CVE-2019-17391
PUBLISHED: 2019-11-14
An issue was discovered in the Espressif ESP32 mask ROM code 2016-06-08 0 through 2. Lack of anti-glitch mitigations in the first stage bootloader of the ESP32 chip allows an attacker (with physical access to the device) to read the contents of read-protected eFuses, such as flash encryption and sec...
CVE-2019-18651
PUBLISHED: 2019-11-14
A cross-site request forgery (CSRF) vulnerability in 3xLogic Infinias Access Control through 6.6.9586.0 allows remote attackers to execute malicious and unauthorized actions (e.g., delete application users) by sending a crafted HTML document to a user that the website trusts. The user needs to have ...
CVE-2019-18978
PUBLISHED: 2019-11-14
An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.
CVE-2019-14678
PUBLISHED: 2019-11-14
SAS XML Mapper 9.45 has an XML External Entity (XXE) vulnerability that can be leveraged by malicious attackers in multiple ways. Examples are Local File Reading, Out Of Band File Exfiltration, Server Side Request Forgery, and/or Potential Denial of Service attacks. This vulnerability also affects t...