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.

Security Management

12/5/2018
09:35 AM
Alan
 Zeichick
Alan Zeichick
Alan Zeichick
50%
50%

IT & OT Convergence: a Potential Security Nightmare

Industrial systems are rapidly connecting to the wider, public Internet. There are a host of security problems that comes with this convergence, however, and combing IT and OT is not the cure. Here's why.

It was the night before end-of-quarter, and all through the plant, factory floor systems were breaking down because IT flagged a security violation on a safe but rarely used industrial process, and sandboxed a critical subnet.

The poetic legacy of Clement Clarke Moore is secure: My rhymes will never achieve the immortality of "A Visit from St. Nicholas," a.k.a. " 'Twas the Night Before Christmas," but that doesn't make this stark warning about the dangers of the convergence of information technology (IT) with operational technology (OT) any less timely.

IT and OT have two entirely separate histories and objectives.

IT largely exists to solve challenges that were historically addressed by quill-and-ink, abacuses, ledger books, file cabinets and typewriters. Providing employee access to Salesforce.com is IT; so is a deployment of Microsoft Office 365, sending and receiving email, building and running websites, social media and engaging in e-commerce.

By contrast, OT is the factory floor and everything involved in it, from forklifts to assembly lines to packaging to shipping. Centrifuges in a pharmaceutical lab, ovens in a bakery, forges in a steel mill, printing presses for a newspaper and computer-controlled lathes.

These are all operational systems.

There is clearly overlap, and there's more overlap all the time, as industrial processes become more interconnected with computers. Internet of Things (IoT) technologies permeate every aspect of OT these days: forklifts, bakers ovens, centrifuges and presses are monitored by computers and controlled by computers. (See Why CISOs Need a Seat at the IoT Projects Table.)

When computer-controlled manufacturing first came on the scene, it was limited in scope, and almost always restricted to a few devices. Those devices often weren't networked at all, or if they were networked, existed on their own industrial-control LANs. Frequently those were proprietary networks, with specialized protocols at every layer of the network stack.

Those OT networks were usually managed by the factory-floor team: The same folks who maintained the printing press also set up and managed its controlling servers, terminals and networks, often with help from the hardware manufacturers. It was a specialized network, and was beyond the realm of the company's IT staff. In fact, there may have been a strict hands-off policy, with minimal interfaces bridging the operational systems with the corporate LAN.

For many reasons, including security, let's keep those worlds separate. Admittedly, it's going to be more difficult, especially if those manufacturing and other operational systems need to access cloud resources -- or if some well-intentioned people want to connect them to the Internet.

You don't want bad actors accessing your ERP systems, your customer database or financial filings. Those would be damaging. But you certainly don't want those bad actors being able to read OT sensors -- or change industrial controllers. That would be disastrous. Imagine the difference between a hacker or foreign agent being able to subvert a water company's billing systems verses being able to launch a distributed denial of service (DDoS) attack against its hydroelectric dam controls. Or being able to change the temperature on a steel mill's furnace. Or being able to control the ventilation on a petrochemical refinery's distillation tower?

Here are seven rules for keeping OT systems safe and secure, and protecting the product, the plants and the people living nearby:

  • Don't connect disparate OT networks to each other. Maintain air-gaps between them
  • Don't connect any OT networks to the corporate IT LAN
  • Don't let IT staff come within 100 yards of any OT networks
  • If OT networks need cloud resources, use dedicated links and keep traffic off the Internet
  • Encrypt everything, even on a controlled network
  • Require strong authentication everywhere. Trust nothing
  • If an executive suggests IT and OT convergence, make sure security is the primary concern, far outweighing cost-savings or convenience

As in the bad poetry above, the IT staff doesn't understand the OT systems, nor is there any reason for them to do so. Keep the good actors out. Keep the bad actors out. You can be sure that St. Nick's OT network controlling the miniature sleigh and eight tiny reindeer can't be hacked by a spearphishing email, or shut down by an over-eager security analyst.

Let's keep it that way.

Related posts:

Alan Zeichick is principal analyst at Camden Associates, a technology consultancy in Phoenix, Arizona, specializing in enterprise networking, cybersecurity and software development. Follow him @zeichick.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.