<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2975524&amp;fmt=gif">
BLOG

ICS Village Series: Aggregating Distributed Industrial Networks

November 11, 2021

oil refinery industry

As ICS/OT environments get upgraded and modernized, challenges surface on deploying asset inventory and threat detection solutions within a distributed network. These include monitoring a network covering a significant geographic location and monitoring locations that cannot support additional hardware and need to utilize existing assets.

In the second of our 3 part ICS Village blog and video series on gaining visibility into your critical infrastructure environments, we are going to focus on overcoming distributed network challenges.

Critical infrastructure organizations are known for their unique and geographically dispersed network environments. Sectors such as water, mining, power distribution and transmission, as well as manufacturing can all face network architectures where you may need to secure various segments from different points within a more extensive network.

In addition, the physical location sometimes cannot support additional hardware within these networks due to space, power, environmental, or budget constraints. So how can organizations add a security solution to a distributed network where the location and the distance may present visibility challenges?


Aggregating SPAN traffic to a central security sensor without affecting infrastructure

For environments that cannot physically add additional hardware like network TAPs or multiple security sensors into the current infrastructure, leveraging SPAN ports to mirror the traffic from managed switches becomes the next best option.

A managed network switch typically includes port mirroring, also known as SPAN (Switch Port Analyzer). This capability programmatically designates ports on the switch to send duplicate copies of the network packets seen on one or more ports to a specified port. On this specified port, a network monitoring solution resides to analyze the packets traversing the network. But, without the capability to add additional hardware or security sensors at each physical location due to space, power, environmental, or budget constraints, the next challenge is how to get the SPAN links from the various areas to a centralized sensor.

As depicted in the diagram below, this use case illustrates how to aggregate various SPAN links down to a centralized Dragos sensor.

Utilizing Garland’s High-Density Aggregator TAP, organizations can aggregate SPAN traffic from four or more distributed locations into one specific device, feeding all the network packet details and contents to the Dragos sensor.



After receiving the packets, the Dragos sensor performs some initial pre-analysis work. It then sends the appropriate metadata over to the Dragos Platform, which typically sits in Level 3 or 4 of the Purdue Model reference architecture, where primary reporting and notifications happen.

This use case incorporates existing switch infrastructure, aggregating the various links through an aggregator TAP and then to the security sensor without affecting the infrastructure.


Aggregating network TAP traffic to a central security sensor from distributed locations

Another use case is to TAP instead of relying on the switch SPAN. Utilizing SPAN can be a common challenge in legacy environments or unavailable on unmanaged switches. Suppose the infrastructure has several fiber optic cables running from various sites coming back into one centralized place. We could deploy passive fiber network TAPs and ultimately aggregate those to the sensor.

Adding plug-and-play network TAPs and traffic aggregation allows the legacy infrastructure to remain in the original configuration to continue safe and reliable operations while providing the packet visibility needed to manage and secure assets without making device modifications. Network TAPs are purpose-built hardware devices, which allow you to analyze network traffic by copying packets, without impacting network integrity.


With this deployment scenario, as seen below, network traffic is being fed to the Dragos Platform. A deployment like this gives a complete asset inventory list and a map view of the various locations of the network like firewalls, PLCs, network switches, HMIs or human-machine interfaces, IP addresses, MAC addresses, and more, spread across an extensive network infrastructure.


These are two good use cases for providing packet visibility and a security platform in a distributed network that minimizes the impact to the infrastructure.

In our third iteration of this blog and video series, we will review how to quickly deploy a proof of concept to simultaneously compare multiple asset inventory and threat detection solutions.

Watch the ICS Village demonstration ‘Aggregating Distributed Networks To Gain Visibility Into Your Critical Infrastructure’

Want more information?

Click here to watch the full ICS Village demo ‘Gaining Visibility Into Your Critical Infrastructure.’ Or explore the Dragos and Garland Technology solution brief here.

See Everything. Secure Everything.

Contact us now to secure and optimized your network operations

Heartbeats Packets Inside the Bypass TAP

If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.

If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.

While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.

Some of you may have noticed a flaw in the logic behind this solution!  You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.

Glossary

  1. Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.

  2. Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.

  3. Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.

NETWORK MANAGEMENT | THE 101 SERIES