Follow these standards-based security best practices to implement a secure and reliable wireless network for mission-critical applications.
The information age’s arrival in manufacturing is significant not only for what data you can access in your manufacturing operations but also how you can access it. Most significantly, wireless technology gives you new freedom to cut the cord, figuratively speaking, and imagine your operations in transformative new ways.
It could involve using mobile devices to monitor your operations from anywhere in the plant or to connect your maintenance technicians to remote experts for faster downtime resolutions. It could involve wireless, Internet Protocol (IP)-enabled cameras that monitor your operations from hard-to-reach areas. It also could involve connecting to wireless connected devices in the ever-growing Industrial Internet of Things (IIoT) to collect quality, safety and other data from your manufacturing processes. Beyond this, because wireless technology reduces hardware and cabling, it lowers installation costs and maintenance demands.
Wireless is not new to manufacturing and industrial environments. It’s been used for years in applications such as point-to-point data transfer and supervisory control and data acquisition (SCADA). But as wireless is increasingly used for mission-critical applications and real-time control, demands on the technology also are changing.
Particularly as more manufacturers build a Connected Enterprise and converge their industrial and enterprise systems into an Ethernet-based network architecture, they need reliable wireless communications with low levels of latency and jitter to achieve uninterrupted control and data access. More than that, they need to confirm their wireless communications are secure.
Given the unique risks that wireless communications face — which include the interception and monitoring of data, wireless frame spoofing, and denial-of-service attacks — security is absolutely essential. This includes using device authentication and data encryption methods that align with IEEE 802.11, which is increasingly becoming the standard for deploying reliable and secure wireless networks for industrial automation and control system (IACS) applications.
When implementing an industrial wireless network, keep in mind some of the following design and security considerations from the guide “Deploying 802.11 Wireless LAN Technology within a Converged Plantwide Ethernet Architecture,” developed by Rockwell Automation and its Strategic Alliance Partner Cisco.
Autonomous vs. Unified
It’s first important to consider the two different wireless local area network (WLAN) architecture types used in IACS settings, as the security considerations are different for each. An autonomous architecture type uses standalone wireless access points to implement all WLAN functions. Each autonomous access point is individually configured and managed. An autonomous architecture typically is used only for small-scale deployments or standalone wireless applications. It has a lower initial hardware cost, simplified design and deployment, and offers more granular control of quality of service to help prioritise IACS application traffic on the network.
A unified architecture is used for large-scale plant-wide deployments that require a range of clients and applications. It offers foundational services, including intrusion prevention and wireless guest access, and provides the foundation for enabling plant-wide mobility.
A unified architecture solution splits functionality between lightweight access points (LWAP) and wireless LAN controllers (WLC). It has “zero touch” deployment and replacement of access points, requires less effort for updating configuration and firmware, and provides centralised control and visibility.
Autonomous architecture security
The Wi-Fi Protected Access 2 (WPA2) security standard with Advanced Encryption Standard (AES)-level encryption is the only security mechanism recommended for industrial WLAN applications. WPA2 offers the most advanced security available today for WLANs in industrial settings, while AES encryption is implemented at the hardware level and doesn’t affect an application’s performance. In an autonomous architecture, WPA2 can support both pre-shared key authentication and 802.1X/ Extensible Authentication Protocol (EAP) authentication. Factors such as your security policy, infrastructure support and ease of deployment can help you determine which of these two authentication methods is most appropriate for your autonomous WLAN.
You also might choose to use multiple authentication methods in a single autonomous architecture, such as to support different client types.
Pre-shared key authentication uses a common password that is shared across all devices in the architecture. Keep in mind, this method can’t restrict access to specific clients – anyone with the password can authenticate to the WLAN. As a result, pre-shared key authentication is best suited for small-scale WLANs in which the clients are tightly controlled. This could include an application containing a fixed number of wireless machines using work group bridges (WGB).
Configuration recommendations for this approach include using the EAP-FAST protocol to authenticate WGBs to the autonomous WLAN. The dedicated access point should be configured as a Remote Access Dial-In User Service (RADIUS) server to store the WGB credentials, but it should not accept any wireless clients.
MAC address authentication is a third method for authentication but isn’t secure when used alone because MAC addresses can be detected and spoofed. Rather than using this as your lone security approach, use it to supplement pre-shared key or 802.1X/EAP authentication as an additional safeguard against incidental connections in critical control applications.
Unified architecture security
A unified WLAN architecture requires certificates and other EAP protocols for authentication beyond what 802.1X/EAP authentication can provide. Additionally, pre-shared key authentication won’t work in a unified architecture because it can’t provide the fast-roaming security that a unified architecture requires.
Unified architectures should use EAP-Transport Layer Security (TLS) authentication for plant-wide WLAN security. This method requires a RADIUS server located in the Industrial Zone Level 3, while local EAP certificates must be supported on the controller.
Additionally, non-roaming applications may not require EAPS-TLS authentication, but using it for both fast-roaming and non-roaming will help simplify deployment and reduce confusion regarding which security method is used for different devices.