Patent Application
20220303253
The present disclosure relates generally to Media Access Control Security (MACsec), and more particularly, to facilitating communication between electronic devices in a power system.
Non-limiting and non-exhaustive embodiments of the disclosure are described herein, including various embodiments of the disclosure with reference to the figures listed below.
One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
Electric power delivery systems include equipment, such as generators, power lines, and transformers, to provide electrical energy from sources to loads. Various intelligent electronic devices (IEDs) may be used in monitoring, control, and protection of the power delivery system. For example, IEDs may obtain voltage measurements and/or current measurements and trip circuit breakers to disconnect electrical equipment to protect the electric power delivery system from exceeding designed operating conditions due to faults.
IEDs may communicate with each other and other electronic devices to facilitate the monitoring, control, and protection of the power delivery system. For instance, IEDs may be connected to a wired Ethernet network, via a network switch, that receives data from a sending IED and forwards the received data to a destination IED. The IEDs may communicate power system data, such as voltage measurements, current measurements, circuit breaker statuses, and circuit breaker commands, among others, to allow the IEDs to better control and protect the power system.
To communicate, IEDs may send the power system data encapsulated into frames of a data link layer of a network. The data link layer may refer to the layer two of the open systems interconnection (OSI) architecture model. To improve security, IEDs may communicate the power system data according to the 802.1AE Institute of Electrical and Electronics Engineers (IEEE) Media Access Security (MACsec) frame format on the data link layer. Data communicated using MACsec frames may include an encrypted payload as well as additional header information. For example, the MACsec frame may include a Sectag that has an optional secure channel identifier (SCI). Within the SCI, a port identifier may be included.
To manage a network of IEDs, some actions may involve physically going to the IED and inspecting the operating state of the IED. IEDs may be located remote from one another or in difficult to reach places. Accordingly, there is a need in the field to allow operators to be aware of the operating state of IEDs without physically going to the device and still ensuring that access to the IED remains secure from unauthorized personnel.
As explained below, MACsec may be used to facilitate communication of device management information, such as network and device identification information. Further, IEDs may communicate device management information automatically (e.g., at predetermined intervals, upon request, or upon changes in state). By automatically communicating network and device identification information via MACsec key agreement (MKA) and MACsec, operators may manage network communication and device operating state without instrumenting the device by being physically present at the device, thereby reducing the difficulties in network and IED management.
As illustrated, the power source 22 may provide power, via a substation 30, to power the loads 24 and 26. The substation 30 includes a transformer 32 that steps up or steps down the voltage to be provided to a bus 34 via power line 36. Various feeders 38 and 40 may be electrically connected to the bus 34 to provide power to the loads 24 and 26 via power lines 42 and 44. Although illustrated in single-line form for purposes of simplicity, power system 20 may be a multi-phase system, such as a three-phase electric power delivery system.
The power system 20 may be monitored by one or more IEDs 50, 52, and 54, although additional IEDs may also be utilized. As used herein, an IED (such as IEDs 50, 52, and 54) may refer to any microprocessor-based device that monitors, controls, automates, and/or protects monitored equipment within the power system 20. Such devices may include, for example, remote terminal units, differential relays, transformer relays, distance relays, directional relays, feeder relays, overcurrent relays, voltage regulator controls, voltage relays, breaker failure relays, generator relays, motor relays, automation controllers, bay controllers, meters, recloser controls, communications processors, computing platforms, programmable logic controllers (PLCs), programmable automation controllers, input and output modules, and the like. The term IED may be used to describe an individual IED or a system comprising multiple IEDs. The IEDs 50, 52, and 54 may obtain electric power system data using current transformers (CTs) 60, 62, and 64, and potential transformers (PTs), and the like. The IEDs 50, 52, and 54 may detect events, such as fault events, on the power lines 36, 42, and 44 using current and voltage signals from the CTs 60, 62, and 64 and/or the PTs. The IEDs 50, 52, and 54 may be communicatively coupled to circuit breakers (CBs) 70, 72, and 74 to send control signals to the CBs 70, 72, and 74 to open (i.e., trip) or close the CBs 70, 72, and 74 based on the power system data.
The IED 50 may further include one or more processors 81, a computer-readable medium (e.g., memory 82), a communication interface 83, a display terminal 84, detection circuitry 85, and output circuitry communicatively coupled to each other via one or more communication buses 87. The processor 81 may be embodied as a microprocessor, a general-purpose integrated circuit, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or other programmable logic devices. It should be noted that the processor 81 and other related items in
In the IED 50 of
In the illustrated embodiment, the IED 50 includes detection circuitry 85 that detects various electrical conditions of the power line 36 based on the input signals. The detection circuitry 85 may include a current conversion circuit (e.g., a transformer) that transform the input signals to levels that may be sampled by the IED 50. The detection circuitry 85 may include analog-to-digital converter(s) that sample the current and voltage signals and produce digital signals representative of measured current and measured voltage on the power line which may be transmitted to the processor 81. The IED 50 may compare the current measurements to thresholds to detect faults and to disconnect the bus 34 from the power source 22. For example, if current on one or more phases exceeds a preset threshold and/or current-over-time exceeds a preset threshold, the processor 81 may detect a fault event and send a signal, via the output circuitry 86, to open the CB 70.
In some embodiments, the IED 50 may include a communication interface 83, such as an ethernet port, to communicate with other IEDs. Further, the IED 40 may include a display terminal 86 and input structures (e.g., Universal-Serial-Bus (USB) ports, buttons, touchscreens, etc.) to allow operators to review events on the power line, change settings, etc.
Each of the IEDs 52 and 54 may have similar components (e.g., processor 81, memory 82, communication interface 83, display 84, detection circuitry 85, and output circuitry 86) to those described with respect to IED 50 to allow the IEDs 52 and 54 to obtain power system measurements, control the CBs 72 and 74, and to communicate. In some embodiments, the IEDs 50, 52, and 54 may communicate power system data via a communication network.
In the illustrated embodiment, the IEDs 50, 52, and 54 may be connected to a switch 80 to form a wired network. The switch 80 may receive frames of power system data from a sending IED and forward the power system data to a receiving IED For example, IED 50 may send and/or receive power system data to or from IEDs 52, and 54, such as voltage measurements, current measurements, and circuit breaker status, among others. If IED 52 were to detect a fault, IED 52 may communicate the fault event to IED 50 and the status of CB 72 via the wired network. If the CB 72 opens, the IED 50 may keep CB 70 closed to allow power to continue to be delivered to load 26. If IED 52 detects a fault and CB 72 remains closed, IED 50 may respond by opening CB 70, thereby isolating the fault. The IED 50 may respond to fault events faster due to the communication network, thus improving the reliability of the power system 20.
The switch 80 may include switching hardware and forwarding circuitry, which may include one or more processors, memory, and communication ports that allow the switch 80 to receive and forward power system data to a receiving device. The switch 80 may be embodied as a managed switch or an unmanaged switch.
The switch 80 may operate as a key server 90 that manages MACsec frame communication on the switch 80 via MACsec keys. In other embodiments, the key server 90 may be embodied as a gateway, a remote terminal unit (RTU), or the like. For example, a gateway may be an electronic device that operates as an access control that authorizes access or prevents unauthorized access onto the communication network from remote devices, such as a supervisory control and data acquisition (SCADA) system 100. The key server 90 may operate using hardware of the switch 80 or the gateway 92 or may include separate hardware to communicate MACsec keys. In certain embodiments, a controller 102, such as an SDN controller, may manage the communication network, based on inputs from a user, by sending control instructions to the switch 80. In some embodiments, the key server 90 may be a part of an intrusion detection system (IDS) that prevents intruders on the network by inspecting the messages.
The Sectag 146 may include an Ethertype 170, a TCl/AN 172, a short len 174, and a packet number 176, which may be used to identify the decryption key and detect transmission of repeated frames. Further, in MACsec frames 140, the Sectag 146 may include a secure channel identifier 178, which is an optional field. The secure channel identifier 178 may include a secure channel sender MAC address 180 and a port identifier (PI) 182. The ICV 150 may ensure the integrity of the MACsec frame 140 by allowing the recipient to detect errors in the transmission process.
As mentioned above, one technique to ensure communication between devices operates as expected is by having an operator inspect the IED However, this process may be time consuming or difficult and may involve an operator being physically present at the IED and/or entering communication settings to enable the devices to communicate. As explained below, MACsec may be used to facilitate communication of device management information, such as automatic device identification, logging, alerting, password management, and device settings. In some embodiments, device management information may refer to device data that is separate from the power system data (e.g., voltages, currents, power, circuit breaker status, etc.) communicated to monitor, controls, and protect the power system.
Following the framework authentication, the MKA process may begin with the peer-to-peer devices selecting a key server. In the illustrated embodiment, the switch 80, the gateway 92, or another device may be selected as the key server 90 (arrow 262). The process may continue with the key server 90 generating secure association keys (SAKs), which may refer to a random value that is generated based on the CAK. The key server 90 may then communicate the SAK to any of the peer connected devices on the communication network 120 (e g, IEDs 50, 52, and 54), thereby establishing a CA between the key server 90 and the IED 50 (arrow 264).
The key server 90 and the IED 50 may then exchange power system data via MACsec frames (arrow 266). The key server 90 and the IED 50 may further continue to send keep alive signals indicating that the CA is still alive (arrow 268). The MKA may be repeated for each of the application protocols that are used to communicate between the key server 90 and the IED 50.
IEDs may be on-line for lengthy periods of times (e.g., months, years, decades, etc.) Further, changes in communication networks may occur, such as adding additional IEDs, removing IEDs, changing passwords, changing operating systems, changing firmware, and updates in logging/alerting systems. One technique to manage changes in the communication network is by having operators change settings at the IEDs. However, such changes may be difficult or time-consuming depending on the number of IEDs, the difficulty accessing the IEDs, etc.
The MKA protocol may also allow for MKA messages to send and receive communication network-management messages that are system-related (non-power system data that indicates how the communication network is expected to operate) and not limited to MACsec frames. For example, MKA messages may include MKA type-length-value (TLV) messages that specify the type of data in the message, the length of the message, and a value (e.g., payload) of the message. Further, MKA messages may contain a parameter set type that indicates the format of the message and a payload in the format associated with the parameter set type.
As explained below, MKA messages may be used to communicate network changes to IEDs and/or other network devices. For example, IEDs may be pre-configured to automatically communicate device information to other devices on the communication network. The automatic communication of device information may be periodically performed to ensure that other devices are able to monitor the communication network.
As mentioned above, the MKA protocol process 260 may be used on a device management CA, separate from the power system CA, to communicate device management information. Further, the IEDs 50 may automatically communicate device management information (arrow 270) upon establishing the communication link (e.g., device management CA). By automatically communicating the device management information, security of the communication network may be monitored without instrumenting the IED The IED 50 may continue to periodically communicate the device management information at preset intervals (arrow 272) to allow for detection of changes in the power system.
The IED 50 may obtain power system data via sensors or other IEDs. The IED may communicate the power system data via the communication network using the MKA protocol described above.
In addition to communicating power system data, the IED 50 may communicate device setting information (e.g., device identification information) on the same CA as the power system data. Alternatively, the IED 50 may form a separate device setting CA with other devices via the switch 80 and/or key server to allow the devices to communicate device information. For example, the IED 50 may establish a device CA with the IDS 304 and other IEDs. Upon establishing the device CA with the other devices, the IED 50 may communicate hardware model, serial numbers, current firmware, operating system, running memory, and settings hashes to the other IEDs and/or the IDS. Further, the IED 50 may periodically announce the device settings to the other CA devices at a preset interval (e.g., once per minute, once per hour, etc.).
The device information messages may be special MKA protocol type-length-value messages, different from power system MACsec messages that communicate MACsec frames, where the MKA message indicates the type of data, the length of the data, and the value. As an example, the MKA message may indicate that the message is communicating a hardware model as the type, the length of the hardware model, and the value of the hardware model of the IED 50.
In another embodiment, the MKA message may be a parameter set-type message that indicates a different message format that is expected to include particular fields. For example, the MKA message may have a parameter set-type indicating device settings and include hardware model, serial number, and firmware in a predetermined order according to the parameter set-type.
By periodically announcing device information to other devices and/or the IDS of the communication network, the IDS may monitor device connections, device settings, and device state. Further, by periodically announcing device identification information, the identification information may be captured by the IDS without querying the IED and without sharing keys by inputting keys at each of the devices while allowing the IDS to identify devices connected to the communication network. In some embodiments, the IDS may notify operators if a device management message is not received from an IED within an expected period of time. For example, if the IDS is expecting to receive a device management message from an IED that is not communicated, the IDS may send a notification to an operator to allow the operator to respond to the missing device management message.
As illustrated, IEDs 300 and 302 may use IED 50 as a proxy and send information to the IDS 304 through the IED 50. That is, IEDs 50, 300, and 302 may each periodically (e.g., each second, each minute, each hour, each day, each week, etc.) send their device identification information to the IDS 304 to allow the IDS 304 to monitor the devices in the communication network 120. In addition to intrusion detection, MACsec and MKA protocol may be used to automatically communicate data that allows for logging and alerting.
As mentioned above, the device may communicate using a separate connectivity association for device messages, such as logging, alerting, device identification, etc. The alerting process may have the option to encrypt the device message with a CAK that can be shared with the IDS 304. The key server 90 may then forward the event information to the log server 310.
As illustrated, during initial MKA adoption negotiation as described in process 260, the IED 50 may announce to the key server that it has a MACsec password management capability that allows the key server 90 to update passwords on the IED 50 by sending updated passwords via MKA protocol. MACsec and MKA protocol may be used to change passwords on the IED over a secure LAN. For example, the key server 90 may send an MKA TLV message or a MKA message with a parameter set type indicating that the message includes an updated password to update each of the passwords on the IED 50. The password change may be encrypted using the KEK derived from the CAK of the CA on the communication network. The CAK may be shared with an IDS system or an automation controller 320 that uses the IED password. The key server 90 may send the MKA message with the updated passwords to the switch 80, and the switch 80 may provide the MKA message with the passwords to the connected devices, such as IED 50 and the automation controller 320. The password communication may be sent on a separate password management CA, a device management CA, or the power system data CA. By communicating device management information using the MKA process, IDS and password management systems may allow operators to protect the communication system without having an operator physically be present at the IED. Further, automatically communicating the device management information upon MKA initialization and/or at periodic intervals may allow IDS systems to detect changes in the communication network, thereby improving the security of the communication network.
The specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.
The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function] . . . ” or “step for [perform]ing [a function] . . . ”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).
