SB Securing Ot Networks With Microsegmentation
SB Securing Ot Networks With Microsegmentation
SB Securing Ot Networks With Microsegmentation
Securing OT Networks
With Microsegmentation
The PCN transmits instructions and data between control and measurement units and interconnects various components
within an ICS/OT environment. They are high-performance, robust, and deterministic LANs. A PCN must maintain constant
availability, rapid response, robust error checking, and correction to ensure zero downtime and enable the deterministic,
error-free, and continuous operations of an ICS.
To achieve the determinism and robustness requirements of an ICS, PCNs are often configured in flat network structures with
little or no boundary limits between the different components of an ICS, as shown in Figure 1. This inherently flat network
structure of the PCN makes it faster and easier to maintain.
HMI
1
SOLUTION BRIEF | Securing OT Networks With Microsegmentation
The zone and conduit model is introduced in International Society of Automation (ISA)/International Electrotechnical Commission
(IEC) 62443-1-1 and IEC 62443-3-2 and provides detailed guidance on how to define zones and conduits. Additionally, the
Purdue Enterprise Reference Architecture (PERA) framework can be used to segment the various zones and conduits within an
ICS into multiple levels.
Zone A Zone B
Conduit
In a converged ICS/OT and IT infrastructure, communication is no longer based on proprietary network communication protocols
or even simply ICS/OT-specific communication protocols. Instead, the converged ICS/OT and IT network relies on a combination
of complex proprietary and open standard communication protocols that are inherently vulnerable to various attacks. This
2
SOLUTION BRIEF | Securing OT Networks With Microsegmentation
expands the network’s attack surface and makes traditional security controls, such
as VLANs, insufficient for ICS, especially as OT and IT networks converge.
The zero-trust security
Although defining zones and conduits and segmenting networks into levels are model states that all
essential for ICS/OT and IT convergence, it doesn’t entirely address network attempted connections to an
security challenges within a converged infrastructure. VLANs are not sufficient to organization’s system should
prevent sophisticated network attacks. be verified before granting
access, whether they come
VLANs freely forward network packets to devices that are part of the same
from inside or outside the
broadcast domain. Every packet that needs to travel beyond the broadcast domain
organization’s network. The
boundary requires a network routing mechanism. Typically, the routing mechanism
same zero-trust security
acts as a virtual or physical conduit and is sometimes used to implement security
concept is followed in
controls, such as network traffic inspection, to control communication between
ICS/OT infrastructure
the two broadcast domains. While VLAN routing mechanisms offer some security
to whitelist the network
benefits, they are insufficient in modern ICS/OT and IT converged infrastructure.
communication between
VLANs also fail to inspect the network communication within the same broadcast different ICS components.
domain. Within a broadcast domain, the devices that are part of a VLAN can
unrestrictedly communicate with one another without these communications being
inspected or controlled.
In a typical ICS/OT network deployment, there are dozens of components grouped together in a single VLAN, and these
components can freely communicate with one another without going through a routing conduit. This enables any anomalous
network communication to move laterally within the PCN.
Once these networks are converged with other networks, usually outside the ICS/OT boundaries, it becomes critical to inspect
each and every communication channel. Otherwise, attacks on the network could remain undetected due to complex network
integrations. Moreover, the use of open communication protocols for exchanging information between the ICS/OT and IT
networks introduces additional risk, where weakness in the communication protocol design and the availability of exploits can
provide a vector to attack ICS/OT environments.
Firewall FortiGate
VLAN 1 VLAN 1
VLAN 1 VLAN 1
FortiSwitch FortiSwitch
Figure 3: Normal VLAN routing vs. microsegmentation using Fortinet FortiSwitch and FortiGate.
3
SOLUTION BRIEF | Securing OT Networks With Microsegmentation
The Fortinet integrated solution for microsegmentation also uses PERA guidance for solution deployment. The
microsegmentation can be implemented at any level within the ICS/OT network as long as there is network connectivity between
the various components of the ICS.
Level 2
Supervisory
Control Network
Engineering workstation Operator PC
Level 0
Physical Plant Floor
Instrumentation
Bus Network
Normal VLAN traffic blocked Fortinet traffic flow with NGFW inspection
Figure 4: Sample Fortinet FortiSwitch and FortiGate microsegmentation PERA deployment architecture.
4
SOLUTION BRIEF | Securing OT Networks With Microsegmentation
Conclusion
ICS/OT networks are largely composed of long life-cycle devices with unique operating requirements. They require an OT-specific
approach to security.
Fortinet has demonstrated that it has a unique perspective on ICS/OT network security, which enables Fortinet to combine
insights with OT-specific threats tracked by FortiGuard Labs into OT-specific security threat reports and to develop solutions
that uniquely meet the needs of OT environments.
VLAN-based microsegmentation enables ICS to control business risk while benefiting from a logically segmented network.
The Fortinet Security Fabric is essential to tying these solutions together and providing the security team with full, centralized
visibility and control over all of their security infrastructure.
www.fortinet.com
Copyright © 2021 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product
or company names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other
conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract, signed by Fortinet’s General Counsel, with a purchaser
that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any
such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify, transfer, or otherwise
revise this publication without notice, and the most current version of the publication shall be applicable.