Security: How IT and Industrial Control Differ

Jan. 23, 2013
When your “nail” is computer system security, the “hammer” is often commercial IT security measures.

And though a good dose of IT security is essential to industrial control system security, successfully securing a control system requires additional steps.

A recent release from Tofino Security highlighted the unique aspects of industrial control systems that set their security measures apart from most IT systems. Some of these factors included control systems placement on the plant floor, rather than a climate controlled data center; their potential for placement in or close to hazardous environments; plus the fact that the average life span of equipment on the plant floor is measured in decades rather than a few years.

Referencing information from a Belden Industrial Ethernet Infrastructure Design Seminar, the Tofino release boiled down the differences between IT and ICS (industrial control system) security solutions to the fact that each system has different:
• Performance requirements;
• Reliability requirements;
• Operating systems and applications;
• Risk management goals;
• Security architectures; and
• Security goals.

Security goals are an essential difference between the two.  For example, the number one goal of IT security is focused on privacy, i.e., protecting the data; whereas the number one goal of ICS security is based on safety, i.e., protecting the process. Three major categories of ICS security issues are outlined in the seminar. Those issues are:

Soft targets. According to Belden, control networks are full of what are known as  “soft” targets—devices vulnerable to disruption through their network interface.

Multiple pathways. These pathways often bypass existing security measures in the plant, and some don’t even appear on a network diagram.

Flat networks. Many ICS networks are still implemented as large, “flat” networks with no isolation between unrelated subsystems.

>> David Greenfield, [email protected], is Media and Events Director for Automation World. 

About the Author

David Greenfield, editor in chief | Editor in Chief

David Greenfield joined Automation World in June 2011. Bringing a wealth of industry knowledge and media experience to his position, David’s contributions can be found in AW’s print and online editions and custom projects. Earlier in his career, David was Editorial Director of Design News at UBM Electronics, and prior to joining UBM, he was Editorial Director of Control Engineering at Reed Business Information, where he also worked on Manufacturing Business Technology as Publisher. 

Companies in this Article

Sponsored Recommendations

Rock Quarry Implements Ignition to Improve Visibility, Safety & Decision-Making

George Reed, with the help of Factory Technologies, was looking to further automate the processes at its quarries and make Ignition an organization-wide standard.

Water Infrastructure Company Replaces Point-To-Point VPN With MQTT

Goodnight Midstream chose Ignition because it could fulfill several requirements: data mining and business intelligence work on the system backend; powerful Linux-based edge deployments...

The Purdue Model And Ignition

In the automation world, the Purdue Model (also known as the Purdue reference model, Purdue network model, ISA 95, or the Automation Pyramid) is a well-known architectural framework...

Creating A Digital Transformation Roadmap Using A Unified Namespace

Digital Transformation has become one of the most popular buzzwords in the automation industry, often used to describe any digital improvements to industrial technology. But what...