Loading
Magazine
Recent ActivityRecent Activity

Vital Cybersecurity Info for Food & Beverage Firms

Developing a systematic patch management strategy can be crucial to minimizing cyber risks, especially for legacy systems that aren’t immune to cyberattacks.

Share This:

LinkedInLinkedIn
TwitterTwitter
FacebookFacebook
PrintPrint
EmailEmail
Main Image
Magazine
Recent ActivityRecent Activity
Vital Cybersecurity Info for Food & Beverage Firms
Developing a systematic patch management strategy can be crucial to minimizing cyber risks, especially for legacy systems that aren’t immune to cyberattacks.

Share This:

LinkedInLinkedIn
TwitterTwitter
FacebookFacebook
PrintPrint
EmailEmail

By Mark Cristiano, network and security services business development manager, Rockwell Automation

 

The food and beverage industry has seen great momentum when it comes to addressing cyber hygiene — the starting point for industrial control system (ICS) cybersecurity. Where we used to have a lot of conversations about network infrastructure, cybersecurity techniques and strategy are now taking center stage. But how did we get here?

The problem dates back 20-30 years, when the food and beverage industry was rapidly adopting advanced, proprietary technology on the factory floor. Due to the closed and isolated nature of these systems, cybersecurity was not a true concern.

Fast forward to the past 10 years, and the proliferation of ICS and Ethernet-connected equipment has revolutionized productivity, quality, compliance and speed to market. It has also simplified connection of these legacy systems to each other and to new systems. This open, unmodified Ethernet communication brought increased cyber risk and a new concern: legacy system patch management.

A recent Food Protection and Defense Institute report details how this outdated legacy equipment can expose your operation to malicious attacks. Ones that can disrupt business, destroy equipment and compromise worker and product safety. A holistic cybersecurity program has become a business imperative, and the patch management process plays an important role.

Take Inventory

The idea of an asset inventory isn’t new, and you may have already tried this exercise internally, or even enlisted outside help. But to capture everything is no easy task, and many still are working to get it right.

There are two ways to take inventory. And to set the right foundation for your ICS cybersecurity program, you need both.

  1. Electronic interrogation tools can scan your network and automatically identify assets. This will identify the bulk of assets.
  2. Manual identification will catch the rest, but requires someone to literally walk around, open panels and physically survey assets.

It’s important to use both approaches at all of your locations. If you only inventory nine of your 10 sites, I can just about guarantee the breach is coming through the one that was overlooked.

Set a Comprehensive Patching Strategy

Following the inventory, you might be left with a list of thousands of assets to wrap your head around. Luckily, not all assets are created equal. The next step is performing a risk analysis to identify the high priority assets to patch based on their criticality, exposure, age, anticipated risk, etc. Some assets aren’t even on the network, so are they really a risk?

2020 Networks and Security eBook
Main Image
eBook
2020 Networks and Security eBook

Get tips on how to get started with industrial analytics that help drive better performance; learn the basics of digital twins; and learn how to use edge computing and how it compares to the cloud.

Download Now

You’ll need to address two types of patches:

  1. Operating system (OS) patching is commonplace for IT, so much so that Microsoft Patch Tuesday has been around for more than 15 years. You’ll have to time plant floor OS patching with scheduled downtime for minimal disruption. Some proactive IT/OT collaboration can take care of this in many instances.
  2. Application-level patching is a different story. There could be literally hundreds of applications from different vendors with different patches. So, it’s incumbent upon you to go find patches on vendor websites, understand the vulnerabilities they protect against and if they are needed or not.

Because each application is configured differently, patching the application layer warrants a very deliberate, consistent testing standard — one conducted in a lab environment prior to implementation on the plant floor where you could run the risk of unintentionally shutting down production.

A Systematic Approach

The “fingers crossed” approach is common throughout the food and beverage industry — not for lack of trying, but for lack of the right resources and specialized expertise. Generally, what I see in the field is reactive, such as responding to a high-priority patch notification by shutting down production on a weekend as needed.

And the common progression looks like this:

  • Operations enlists IT to help manage OT patching.
  • IT fills in, but doesn’t have the ICS expertise or resources to manage the unique requirements and constraints.
  • So, they hire a hybrid IT/OT resource, or more often, outsource to a company like Rockwell Automation or others.

Patch management is one step on your way to getting a security operations center up and running.


If going the third-party route, seek a partner grounded in operations. One telltale sign is their service level agreement (SLA) response time. Traditional IT providers measure response in hours. But that kind of downtime in consumer goods production can mean millions of dollars lost. SLAs measured in minutes represent an operations-friendly approach.

The End Game

Patch management is one step on your way to getting a security operations center (SOC) up and running. An SOC can help provide a holistic dashboard view of your security posture, include a disaster recovery strategy and help ensure optimal operation of your connected factory.

In addition, solutions exist that are designed for end point protection or “whitelisting.”  While these solutions do not entirely eliminate the need for patching, they are an effective solution to protect and buy you time while formulating a patching strategy.

The truth is, there is no silver bullet to effective cybersecurity. That is what defense-in-depth (DiD) is all about. But with more than the bottom line at risk (think food and employee safety), reaction and a little luck is no longer a viable approach.

 

The Journal From Rockwell Automation and Our PartnerNetwork™ is published by Putman Media, Inc.

Tags: Food & Beverage
Subscribe

Subscribe to Rockwell Automation and receive the latest news, thought leadership and information directly to your inbox.

Subscribe
  • Sales
  • Customer Care
  • TechConnect Support
  • General Questions
  1. Chevron LeftChevron Left Home Chevron RightChevron Right
  2. Chevron LeftChevron Left Company Chevron RightChevron Right
  3. Chevron LeftChevron Left News Chevron RightChevron Right